Five categories
Services describe how we work. Solutions describe what gets built. Nearly every engagement lands in one of five categories — what your customers touch, what your team operates, what moves money, what makes the system intelligent, and the programmes that hold an estate together.
- Categories
- 5
- Disciplines behind them
- 12
- Delivery
- One senior team
- Engagement
- Project or programme
Where to start
Find your situation. It points at the category.
Most projects announce themselves as a symptom rather than a specification. These are the ones we hear most often, and where each one usually lands.
- Customers email your team to ask where their order, case or project stands.Customer Platforms →
- The business runs on a spreadsheet that only one person is allowed to sort.Internal Systems →
- Your store is a theme you can no longer customise without breaking checkout.Commerce →
- A full-time role is spent copying values out of PDFs into another system.Intelligence →
- A system built in 2013 is now understood by exactly one employee.Enterprise →
- Two departments reconcile the same numbers from two different tools every month.Internal Systems →
- You want subscriptions alongside one-time purchases without a re-platform.Commerce →
- Field staff need the product on a phone, in places with no reliable signal.Customer Platforms →
- Support answers the same twenty questions from answers buried in a wiki.Intelligence →
- Nothing ships until it clears security review, SSO and an audit requirement.Enterprise →
Several of these at once is normal. Programmes usually start in one category and extend into the next once the first system is carrying real traffic.
Describe your situation →Customer Platforms
Client portals, marketplaces, booking platforms, mobile applications.
Everything your customers touch directly. These systems are judged in seconds — sign-in, first meaningful screen, the one action the user came to complete — and they carry your brand at the point where it matters most.
What it includes
- Client portalsAuthenticated access to data, documents and status that currently moves by email.
- MarketplacesMulti-sided platforms with supply, demand, trust mechanics and payments.
- Booking platformsAvailability engines, holds, payments and confirmation flows that cannot double-book.
- Mobile applicationsiOS and Android products with offline behaviour, push and wallet integration.
- Membership systemsTiering, entitlements, renewals and the experience that justifies them.
What changes for the business
01.1
Self-service replaces inbound support volume
01.2
A measurable drop in time-to-first-value for new customers
01.3
Customer data captured as product signal instead of scattered across inboxes
Typical stack
- Next.js
- React Native
- Swift
- Kotlin
- PostgreSQL
- Stripe
Next step
Scope a customer platform →Internal Systems
Dashboards, management platforms, CRM, ERP, internal tools.
The software your team lives in eight hours a day. Internal tools rarely get product-grade attention, which is exactly why they become the bottleneck. We treat them as products with real users.
What it includes
- Operational dashboardsLive views built around decisions, not around whatever the database exposes.
- Custom CRMPipeline and relationship management shaped to your sales motion.
- ERP and back-officeInventory, orders, fulfilment and finance operations in one system.
- Admin and support consolesSafe, audited tooling so support can resolve without engineering.
- Workflow enginesApprovals, routing and escalation with a complete audit trail.
What changes for the business
02.1
Operations capacity decoupled from headcount growth
02.2
One system of record instead of reconciled spreadsheets
02.3
Support resolution without engineering escalation
Typical stack
- React
- TypeScript
- Node.js
- PostgreSQL
- Temporal
- Datadog
Next step
Scope an internal system →Commerce
E-commerce, payment systems, marketplaces, subscriptions.
Systems where a bug has a currency value. We build commerce infrastructure that is fast at the front and correct at the back — idempotent payment flows, reconciliation, and subscription logic that handles the exceptions.
What it includes
- Headless storefrontsCustom front-ends over Shopify or bespoke commerce backends.
- Payment infrastructureCheckout, split payments, payouts and reconciliation.
- SubscriptionsPlans, proration, dunning, pauses and upgrade paths that behave.
- Marketplace commerceMulti-vendor catalogues, connected accounts and payout schedules.
- Merchandising toolsBack-office control over pricing, promotions and product data.
What changes for the business
03.1
Conversion improvement traced to measured performance work
03.2
Revenue operations that reconcile without manual intervention
03.3
New commercial models launched without re-platforming
Typical stack
- Next.js
- Stripe
- Shopify
- Algolia
- PostgreSQL
- Vercel
Next step
Scope a commerce build →Intelligence
AI applications, analytics, automation, recommendation systems.
Turning data and models into product behaviour. Grounded in your own data, bounded by explicit tool permissions, measured with evaluation sets, and designed to fail gracefully when a model is unavailable or wrong.
What it includes
- AI agentsTask-scoped assistants with defined tools, guardrails and human handoff.
- Retrieval systemsSearch and answers grounded in your private corpus with citations.
- Document intelligenceExtraction, classification and validation pipelines with review queues.
- Recommendation enginesRanking and personalisation tuned against real business metrics.
- Analytics platformsWarehouses, pipelines and interfaces that answer operating questions.
What changes for the business
04.1
Manual processing hours converted into reviewed, automated throughput
04.2
Model spend that is observable and bounded per feature
04.3
AI features that degrade safely instead of failing loudly
Typical stack
- Python
- OpenAI
- Anthropic
- Google AI
- pgvector
- Snowflake
Delivered with
Next step
Scope an intelligence build →Enterprise
Large-scale custom software and integrations.
Programmes where the technology is only part of the difficulty. Multiple stakeholders, existing systems that cannot be turned off, security review, and a migration that has to happen without an outage.
What it includes
- Platform modernisationIncremental replacement of legacy systems with a working path at every step.
- Systems integrationConnecting ERP, CRM, identity and data platforms into one coherent flow.
- Identity and governanceSSO, SCIM, granular permissions and complete audit logging.
- Data platformsWarehouse architecture, pipelines and governed reporting.
- Migration programmesDual-run strategies, backfills and cutover plans with rollback.
What changes for the business
05.1
Legacy dependencies retired without a big-bang cutover
05.2
A single identity and permission model across the estate
05.3
Architecture documentation that survives the delivery team
Typical stack
- TypeScript
- Python
- AWS
- Terraform
- Snowflake
- PostgreSQL
Next step
Scope an enterprise programme →— Next
Tell us what needs to exist.
Send the situation, the constraint and the date it has to be live. You get an approach, an architecture and a realistic range — not a brochure.