Our Clients
A client list only tells you a category exists; it does not show how the work actually runs. This record favours the shape of a client base over a headline number: which sectors are represented, how a relationship develops, and who this practice is a poor fit for.
Five sector groups make up the current spread
The client base clusters into five recognisable groups rather than one generic industry claim: regulated finance, healthcare products, logistics and industrial operations, product and workflow SaaS, and learning platforms. Each group carries its own constraint, from a regulator to a classroom, and the engineering discipline applied adjusts to that constraint.
Regulated finance
A fintech ledger operator building compliance-aware software where every release needs an audit trail attached.
Healthcare products
A patient-facing platform where a workflow change has to clear a clinical safety review before it ships.
Logistics and industrial operations
A logistics platform and an industrial manufacturer, both connecting physical operations to the software planning around them.
Product and workflow SaaS
A subscription product scaling through funding rounds, alongside a workflow vendor automating internal approvals for its own customers.
Learning platforms
An EdTech operator serving real classrooms, where downtime lands on a lesson plan rather than a dashboard.
Engagement shape varies more than the sector does
Sector explains the constraint; it does not explain how the work gets staffed. Some clients commission a fixed-scope build for a defined outcome. Others embed a dedicated team inside their own sprint process. A smaller group hands over an operation that is already live and simply needs to keep running.
01Priced and boundedBuild a defined system
A fixed scope and price against a stated outcome, suited to a single new system or a migration.
02Inside your own processExtend an existing team
Engineers join a client's own sprint cadence and standards as additional capacity, not a separate outside crew.
03A structural rebuildModernise what already runs
An ageing system gets rebuilt in place, in stages a client can approve, while it keeps serving live traffic.
04After launch, not beforeRun what already exists
A live system gets a named owner watching cost, incidents and small improvements once the build has shipped.
Most relationships follow the same three stages
A new client relationship rarely starts with a signed statement of work. It opens with a scoping conversation, moves into a delivery phase staffed against whichever shape fits, and settles into a lighter cadence once the system is live.
Scope before committing
A priced conversation turns an ambition into an architecture and a number either side can approve or decline.
Build against a named shape
Delivery runs as one of the shapes described above, staffed and reviewed against the outcome that was scoped.
Settle into a steady state
Once a system is live, contact narrows to a named owner watching cost, incidents and the next small change.
Some engagements are better served elsewhere
A team this size is not the right answer for every request, and saying so early saves both sides a wasted conversation. A single afternoon of freelance work or a fixed low-cost build with no room for review belongs somewhere else.
Very small one-off tasks
A single afternoon of freelance work does not carry enough scope for a reviewed delivery process to add value.
Price with no room for review
A fixed bid that excludes a second engineer's review or automated testing removes the checks this practice will not skip.
A name, not a team
Work that specifically needs one named freelancer rather than an accountable delivery team is a different kind of hire.
A sector spread shown honestly, pending client approval.
These entries preview the sectors and engagement shapes a client base actually represents. Each one is marked as a sample until the named client confirms it in writing, and full evidence replaces every preview as that confirmation lands.
Explore case studiesA compliance-aware ledger product built for a UK and EU fintech operator, engineered with an audit trail in every release.
Sample · pending client approvalA patient-facing product team building healthcare software where every workflow answers to a clinical safety review.
Sample · pending client approvalA European logistics SaaS platform running fleet and warehouse workflows that cannot tolerate a dropped update.
Sample · pending client approvalA US EdTech platform serving real classrooms, where an outage lands on a lesson plan, not a dashboard.
Sample · pending client approvalA European industrial manufacturer connecting plant-floor systems to the software that plans around them.
Sample · pending client approval
A subscription platform re-architected without pausing new feature work.
Aster North needed to scale a multi-tenant SaaS product through consecutive funding rounds. Delivery ran as a dedicated team embedded in their own sprint process, shipping infrastructure changes alongside roadmap features.
- Delivery shape
- Dedicated embedded team
- Feature velocity during migration
- Maintained
Internal approval workflows rebuilt as one configurable engine.
Orra Systems ran approval logic as scattered scripts across several products. A shared workflow engine replaced them, so a new approval rule ships as configuration rather than code.
- Engagement shape
- Fixed-scope delivery
- New approval rules
- Configuration, not code
Asked before reading the sector previews.
01Why are client logos marked as samples instead of live?
Each logo needs the named client's written permission before it can display in production, and that permission is still being collected. Marking it clearly is more honest than displaying a logo nobody has confirmed.
02Can I see a fuller case study instead of a preview?
Named case studies with measured, client-signed outcomes sit on a separate record once that client approves publication. This record links to it once individual approvals are confirmed.
03Do you only work with companies in these five sectors?
These five groups describe the current client base, not a limit on who can be served. A sector outside this list still runs through the same scoping and delivery process.
04What is the difference between extending a team and running an operation?
Extending a team adds engineers to a client's own sprint process for ongoing build work. Running an operation instead takes over something already live, watching cost, quality and incidents under a named owner.
05How small can an engagement be before it scales into a full team?
It can start as a single priced scoping conversation with no commitment beyond that first answer. Many clients only add a dedicated team once the scoping work confirms the shape of the build.
06Would you turn down a project you could technically deliver?
Yes, and the poor-fit examples above describe why: no room for review, a single tiny task, or a need for one named freelancer rather than an accountable team. Saying so early avoids a wasted conversation.
07How do you decide which sector group a new client joins?
By the constraint that actually shapes their software, such as a regulator, a physical operation or a classroom, rather than a generic industry label. That constraint is usually clear within the first scoping conversation.