Services

Define

We agree the one question the week will answer, such as where your customers get lost, and the price, before the week starts.

Design

We draw the product, the screens and the brand so they hold together instead of reading as a patchwork.

Develop

We build what we design. Watching our own designs fail in use is how they get better before they reach you.

Demo

An answer to the one question, with what we expected and what would have proved us wrong written down first.

You hold the files you can open: the drawings, the type, the color values and the rules for using them. If it earns more, a prototype you can click through and use comes next, and you can stop after any week.

Define

Most people start with an assessment or a prototype, agreed and priced before the week begins. The prototype is the first real piece.

Design

We choose the smallest piece that does one useful thing, so you can put it to use rather than wait and trust.

Develop

We build it over the week, and you can open what has been built at every step.

Demo

Each week ends with something you can open and use, and you decide then whether to go on.

You hold the code and the records, written so someone else can take them over. We tell you what hosting, security and upkeep will cost you each month before you decide.

Define

Before the week begins, we write down what we expect to find and what result would show us wrong.

Design

We set the question against your records and the public sources, and keep a note of each figure’s source and date as we go.

Develop

Five working days in your records and in the public sources.

Demo

What we found, what it means, what we would do next, and anything that went against us.

The report, the numbers and the sources are yours to keep and show anywhere, each figure with where it came from and the date. If the data doesn’t answer your question, the report says so, and you can stop there.

Define

Before the week begins, we write down what result would mean no, so the answer can’t be bent afterward to look like a yes.

Design

We keep some of your examples back where the model can’t see them, to score it on later.

Develop

We test the idea on your own work, and we show you what each model run costs before it runs.

Demo

An answer to the one question, scored only on examples the model never saw. When a model isn’t worth building, we say so plainly.

You keep the examples, the scores and the code. If the prototype earns more, it is built in weekly steps, and you can stop after any week.

Define

We pick one repeated task, and write down what we expect to find and what would tell us we were wrong.

Design

We sit with the task as it really happens and count the places it is copied by hand.

Develop

The prototype automates that one task, working, for you to open and use. Anything that goes out under your name waits for your yes.

Demo

What we found, what it means, and what to do next, including the case where the answer is that it is not worth automating.

The scripts and the records are yours, in files and folders you already use. If the prototype earns a second task, that is another week at the same price, agreed before it starts.