Custom builds
You need something that does not exist yet.
A module inside a system you already run. A tool nobody sells. A site for a business that has nothing to do with restaurants. If you can describe it in a sentence, that is enough to start.
The problem
The thing you need is too small to sell and too specific to buy.
How this usually goes
- You explain it in a sentence and get quoted a discovery phase.
- The software you already pay for nearly does it, and everyone has quietly agreed to live with the workaround.
- You get a number back that ends the conversation.
- Nobody has built it because it only matters to you, and you are not a big enough market.
Why one person can say yes
An agency has to cover a team before it covers your problem, which is why small jobs get priced until they go away. There is no team here, so a two-week build is a two-week build rather than a rounding error somebody has to justify.
That is also the honest limit. It means we take on fewer things, and we will tell you when yours is one we should not take.
What we take on
Four shapes of work.
All on the same terms as everything else: nothing upfront, nothing until it goes live.
- A new module in a system you already run Something the platform should do and does not. This is most of the work: the team app has grown by fourteen modules, one request at a time.
- A system that does not exist yet A whole tool built around how you actually work, rather than the shape of somebody else's product. Priced at $300 a month, up to five API integrations.
- Making two things talk Your point of sale, your booking system, your spreadsheet and the thing you type into twice. Integration work is usually the cheapest big win available.
- Personal and small-business sites A real site, hosted, maintained and updated when you need it, for $40 a month. No page builder to fight and no annual renewal surprise.
Proof this is not hypothetical
The biggest build here started as a custom job.
The team platform on this site was not a product anyone set out to sell. It was one operator asking for one thing, then another, until it had grown into fourteen modules used by around two hundred and fifty active people across three locations.
The second system is not a restaurant at all. It is the guest-facing software for an entertainment venue: self-service registration on tablets, waiver capture with signature, payment at the kiosk, membership look-up and digital wallet passes. It runs on a real floor with real guests.
Neither of those existed as software you could buy. Both started with somebody describing a problem in a sentence.
When we will say no
- When we are not certain we can build it. You get told that, not a quote.
- When it needs a team we do not have, or a specialism we do not have.
- When something you can already buy does it properly. We will name the thing and you can go and buy it.
A no on the first call costs you an email. A yes you should not have been given costs a great deal more.
How pricing worksTell us the thing you have already been told no about.
Three fields and a sentence about what you need. We read every one within one business day, and if we are not the right fit we will say so and point you somewhere better.