Open for Briefs
Let's Build Something Useful.
A few paragraphs is enough to start. The reply you get is a view on the work — the first thing we would build, the parts we would leave out, and the questions that decide everything after.
Send a brief
Tell us what you're building.
A few sentences is enough to start. The more specific you are about the outcome, the more useful the first reply will be.
Before You Send
What makes a brief answerable
A brief does not need a specification document behind it. Three things turn a short message into something we can answer properly — the rest can be worked out in conversation.
-
The outcome, not the feature list
Say what has to be true once this ships — the decision that gets faster, the manual step that disappears. Features are one implementation of that, and often not the cheapest one.
-
What already exists
The systems this has to live beside: the ERP nobody is replacing, the spreadsheet quietly running a department, the database you inherited. Integration work moves an estimate further than screen count does.
-
Constraints you already know
A budget range, a date that genuinely matters, a compliance rule, a vendor you are locked into. Constraints are not bad news — they narrow the options down to the ones worth costing.
Straight Answers
What we say early
Some of what we send back is not what anyone hopes to read. These three come early, while they are still cheap to act on.
- 01
When you do not need us
If an existing product already covers the requirement, we will say so and name it. Building a worse version of software you could licence instead is not a project worth selling.
- 02
When the ask is the costly route
A requested feature is sometimes the expensive way to get a result that something simpler already delivers. You hear that before it is estimated, rather than after it is built.
- 03
When the answer is not yet
Some work is blocked by something else: data that is not in shape, a decision nobody has made, a system mid-migration. We will name that rather than quietly build around it.
Starting Out
Questions people ask first
How do you scope a project?
By working backwards from the result to the smallest build that produces it. Where a brief is still open-ended, a discovery phase settles the scope before anyone commits, rather than a proposal guessing and the difference surfacing halfway through.
Who will I actually be talking to?
The people who would do the work. Whoever reads your brief is the one who would architect, design or build it — there is no account layer relaying messages in both directions.
What happens to my idea and the IP?
Yours before you send it, yours afterwards. We will sign an NDA first if you want one, and ownership of what we produce is settled in writing before the build starts — our default position is that it transfers to you.
Can we start small?
Yes — one service, one integration, or a prototype that tests the riskiest assumption is a legitimate way in. A small first piece also answers the question the larger programme depends on: whether it is worth running at all.