Blue SquareBegin the setup guide

Blue Square

Built to order. Paid when you have seen it work.

A website, an app, the chores of the day, or nearly anything else a small business needs: built to your signed specification and paid for only when you have watched it work.

Begin the setup guideA few short screens. Nothing to pay until you have watched it work.

What we build

  1. 01

    The shopfront

    A website designed from a brand book your own answers produce: your facts, your voice, your pages with one job each. Shown live at a preview address; you pay when you have seen it.

    A brand book from your answers, the pages, a preview address on your phone, two revision rounds, the handover.

    Paid when seen
  2. 02

    The app

    We create an app for your business. It runs on your own computer and your own phones, over your own encrypted network: your books, your people paired by a code, your word on what needs approval, a brief each morning. Your data never leaves the building.

    Your books, your people's roles, the morning brief, the backup, your phones paired by a code.

    Paid when witnessed
  3. 03

    Automations

    The chores of the day done for you, inside your app, on your own machine and under your rules. Nothing runs before you have watched it work; then it is paid monthly.

    The trigger, the steps with their rules, a log of every effect, and the undo.

    Monthly, after the run
  4. 04

    Anything else

    An AI voice that answers your phone and books the work. A chat on your site that knows your prices. A 3D view of what you sell. A tool made for one job. If it can be written down and shown working, we build it, or tell you why not.

    One call to scope it, a written plan with its price, then the same rule: you pay when you have seen it work.

    Quoted after one call

What it looks like

Three examples, made to show the work. The businesses in them are examples, not clients; yours is drawn from your own answers.

An example website for a joinery in a warm paper style, the name set large with a pen line drawn around it

A website

For a joinery, in the paper style: the owner's own words, and a pen line that draws itself as the page is read.

An example app on a phone for a cabinetry shop: this morning's summary, two approvals waiting for the owner, and the day's schedule

The app

For a cabinetry shop: the morning's summary, two changes waiting for the owner's approval, the day's schedule. Sample records.

  1. 08:02An enquiry arrives through the website's form
  2. 08:02The customer is added to the books
  3. 08:03A reply goes out in the owner's voice
  4. 09:40The owner drafts the quote in the app
  5. 09:41The quote waits for the owner's approval
  6. 09:58Approved on the owner's phone; the quote is sent
  7. TueA follow-up, unless the customer answers first

An automation

One enquiry, handled: every step logged with its undo, and nothing sent in the owner's name without the owner's word.

How it works

  1. The setup guide.

    You answer it at your pace; an answer you do not know is marked unknown, never invented. It ends in a specification you read and sign.

  2. Four screens, one call.

    First what we refuse; then whether every system has a door, whether every rule can be written down, and whether "it worked" can be seen in data. A no comes with its reason, in writing.

  3. The build.

    From the signed specification, never from the raw answers. A reviewer who did not build it signs that it is fit to show you.

  4. The proof, then the witness.

    A site at a preview address you open on your phone; an app paired to your own phones on your own machine; a workflow run on your systems while you watch.

  5. Payment.

    After the witness. Two revision rounds are inside every build. The only money before a witness is discovery, one call, credited to the build.

We refuse, with the reason written: any job that needs a licence, touches health data, moves other people's money, risks anyone's body, or whose failure would be a lawsuit rather than a loss; and anything on Amazon. We do not sell a builder, an API or an agent you operate: we build, you get results.

Will we take it?

Five questions, a minute. If the answer to any one is yes, we would refuse the job, and the reason is written here as it would be in our letter.

  1. Does the work need a licence to do, as law, medicine or building do?It needs a licence to do. That is the first thing on our refused list, and it stays there.
  2. Does it touch anyone's health records, or could a failure hurt someone's body?It touches health or safety. A failure there is harm to a person, not a loss to a business, and we do not take that on.
  3. Would it hold or move money that belongs to other people, or could a failure end in a lawsuit rather than a loss?It carries other people's money or legal exposure. We build where a failure is a loss you can see and recover from.
  4. Does it run on Amazon: a seller account, listings, publishing, or anything on their platform?It runs on Amazon. We do not touch Amazon accounts; their rulings can close a business overnight, and no build is worth that risk to you.
  5. Do you want a builder, an API or an agent to run yourself, rather than a finished thing that works?You want a tool to operate. We do not sell one. We build the thing, show it working, and hand it over.

Who we are

Everything we make is shown working before it is paid for.

Blue Square builds the three things an owner-run business needs and nobody sells it: a site that is yours, a private app that runs the day on your own machine, and the workflows inside it. We built the app for ourselves first.

Write to us

hello@bluesquare.works

Say what you want built, in a sentence. The setup guide does the rest.

Begin the setup guideOr begin now, and we read your answers before we write back.