Listen
What the business needs, who decides, and what happens on a bad day. Written down and agreed before anything is built.
Software built and sold by the same team.
Four kinds of work. Most projects use two or three of them. We name the ones we are taking on before the contract, not after.
-
Product engineering
Applications built end to end. We take the data model, the interface, the release and the support conversation, so there is no gap between the thing that was designed and the thing that shipped.
Typical shape
- Web applications
- Mobile applications
- Customer portals
- Design systems
-
Platforms and integrations
The work that sits under the product: services that have to talk to each other, data that has to move without anyone noticing, and the legacy system that nobody wants to touch but everybody depends on.
Typical shape
- APIs and services
- Third-party integrations
- Data migration
- Automation
-
Interface design
Interfaces designed next to the people who will maintain them. The test is not how the first screen looks. It is whether the twentieth screen, added a year later by someone else, still belongs to the same product.
Typical shape
- Product design
- Design systems
- Prototyping
- Accessibility
-
Delivery and operations
Releases, monitoring, support and handover. The part of a project that decides whether the other three are remembered well, and the part most teams leave before it starts.
Typical shape
- Release process
- Monitoring
- Support agreements
- Handover
Why the sales team sits in the build
A product is easier to sell when the person selling it has watched it being made. They know which promises are cheap, which are expensive, and which one the engineering team would rather not hear.
The reverse is also true. A developer who has sat in a sales call builds differently, because the customer stops being an abstraction and becomes a person with a deadline.
How an engagement runs
Four movements. We do not start the third one before the first two have produced something you can read.
Shape
Scope in language a buyer and an engineer can both sign. Fixed pieces, assumed pieces, and the order they arrive in.
Build
Short cycles, a demo every week, and a written record of every decision that changed the plan.
Sell
The team that built it takes it to market. Demos, onboarding and the first customers, handled by people who know what is inside.
Where this tends to fit
We are not the right team for every industry. These are the ones where a developer team and a sales team are usually useful on day one.
-
Logistics and operations
Dispatch, tracking, and the internal tools that hold a schedule together once the spreadsheet has stopped working.
-
Retail and commerce
Storefronts, stock, and the quiet systems that decide what a customer sees, in which order, and at what price.
-
Health and clinics
Booking, records, and patient-facing tools where the cost of a confusing screen is higher than in most other work.
-
Professional services
Client portals, document workflows, and the small automations that give a week back to a team that bills by the hour.
Start with a conversation
Tell us what you are trying to build. We will tell you whether we are the right team, and if we are not, what we would do instead.