Bespoke applications
Software built around how the business actually works - data models, roles, screens and reports - rather than a product bent to fit it.
Custom work
Custom development: if it can be built, we can probably build it.
Nearly everything else we do has a package behind it. This does not. Bespoke applications, integrations between systems that were never meant to talk, internal tools, AI assistants. Work with no template, priced after a conversation rather than off a list.
Scope in writing · Fixed price← All service lines
01 / Range
The technical limits are close to none.
We work with web technologies, databases, other people's APIs and infrastructure we run ourselves. The list below is what gets asked for most often - it is not the boundary.
Integrations and APIs
Two systems that have to agree: ERP, accounting, warehouse, courier, marketplace or a supplier feed. With error handling and a reconciliation report rather than a nightly guess.
Internal tools
The spreadsheet, the manual export or the recurring copy-paste, replaced by something that runs on its own and tells you when it fails.
AI assistants and agents
An assistant over your own data and tools, with the boundaries written down - what it may read, what it may change, and what it has to ask about first.
Medusa modules
If a Medusa module is the right home for a feature, it ships as one: its own data models with migrations, a service layer, API routes and an admin page to manage it.
Whatever is not on this list
The list describes the past, not the possible. If your idea fits nowhere above, that is a reason to talk rather than a refusal.
02 / Selection
The limit is not what we can build. It is what we will take on.
We take a project only when we are confident we can do it properly and stand behind it after launch. Sometimes the honest answer is no - and you get it in the first conversation, not three weeks in.
We usually say yes when
- the problem is clear, even if the solution is not yet
- there is someone on your side who can answer questions
- the work can ship in parts and be useful before it is finished
- we can own the outcome, not just the code
We usually say no when
- the deadline needs shortcuts we would regret later
- the scope changes weekly with no decision behind the change
- the work needs access or permissions we would not grant ourselves
- someone else would do it better - we would rather say so
Being told no costs you nothing, and it does not take weeks. If we are the wrong choice you will hear it straight away, and where we can, we will tell you who is the right one.
03 / Price
The price comes out of the conversation.
There is no figure on this page, and that is deliberate. Custom work has no average price - it has a scope, and a scope is something you agree on. So we talk first, write down exactly what it will do, and only then produce a number that does not move.
- 01Conversation
Half an hour about the problem, not the technology. We come out of it knowing whether this is worth building at all.
- 02Scope
A written description of what gets built, what it depends on and what it deliberately will not do. This is the document any later argument is settled against, which is why it is written.
- 03Fixed quote
One price for the scope described, with payment stages and a timeline. A change in scope means a new quote, not a quiet number at the end.
- 04Build
Delivered in parts, with visible progress and the option to stop between stages. What we ship, we maintain.
For larger work we start with a paid discovery - bounded, with a written result, and credited against the project if you go ahead. It is paid because it is work, not because it is a barrier.
Got something in mind?
Describe it in plain words.
You do not need to know how it is built. You need to know what has to happen - the rest is our job.