Maintenance
Keep it running. Dependency and SDK upgrades, security patching, crash triage, an agreed response time.
Services
Five practices, thirty-six services — what each is for, and what you receive. If it is not here, we say so rather than learn it on your budget.
A catalogue lists capability; it does not prove it. No metrics or client stories here, deliberately.
See selected workPractice 01
AI systems that survive contact with production — not demos.
A model capability end users can actually rely on.
Answers grounded in your own documents, with citations.
Software that completes multi-step work, not just answers.
An assistant that resolves work instead of deflecting it.
Data pulled from messy documents at an auditable accuracy.
Cameras and images turned into operational signal.
Forecast what costs money — churn, demand, fraud, failure.
Domain adaptation — after prompting, retrieval and evaluation, never before.
AI in software you already own, without a rewrite.
We build on foundation models and adapt them where evidence supports it. We do not train foundation models.
Practice 02
Making AI land in strategy, tooling, teams and risk.
A scored picture of where you stand.
A sequenced plan with owners and dates.
Choose the stack once and stop paying for shelfware.
Measured throughput from agentic coding tools — Claude Code, Copilot, Cursor.
Ad-hoc prompting turned into a version-controlled team capability.
AI you can defend to a regulator and your board.
Find how your AI gets abused before somebody else does.
Capability built on your actual workflows, not a generic demo.
Governance covers technical and organisational readiness; legal opinions come from your counsel. The people who score your readiness can implement the roadmap — or hand it to your engineers.
Practice 03
The product itself — from first release to multi-tenant scale.
Tenancy, billing and isolation designed in from release one.
In front of real end users inside a quarter.
Web applications your team can still own in three years.
Versioned, documented APIs that others can build on.
SaaS, ERP, CRM and data tools behaving as one.
Complex software made to feel obvious.
Practice 04
Built for the device fleet you actually support.
Android on the current default stack, tested on real devices.
A first-class counterpart, not a port.
One codebase where it saves money, native where it does not.
For an app that is slow, crashing or facing delisting.
Releases stop being a manual event people dread.
In-app AI that stays fast, private and affordable.
Cross-platform is a genuine choice, not one answer: Flutter for pixel-precise interfaces, React Native for JavaScript-strong teams, Kotlin Multiplatform for shared logic under native UI. We write the recommendation down, with its cost. Kotlin and Compose are our Android default.
Practice 05
The foundations that make everything above reliable.
A cloud footprint that is secure and not burning cash.
Ship more often, break less, sleep at night.
Trustworthy data — the precondition for every AI thing next.
AI on rails: versioned, monitored, reproducible.
Evidence that your AI still works on live traffic.
Escape the monolith without stopping the business.
Confidence to release weekly instead of quarterly.
How the work is shaped
Every engagement opens with a written engagement brief: outcome, scope, timeline, practice lead.
| Model | When it fits | How it works |
|---|---|---|
| Fixed-scope project | Scope well defined | Agreed scope, timeline and outcome, quoted after discovery. |
| Flexible delivery | Scope will evolve | Work done at agreed rates; scope adapts each sprint. |
| Dedicated product team | Multi-quarter product work | A cross-functional squad reserved for you, monthly. |
| Embedded specialists | You have a team, missing a skill | Named specialists join your team, under your management. |
| Ongoing partnership | Maintenance, SRE, AI operations | Fixed monthly capacity, agreed response time, shared backlog. |
| Discovery sprint or workshop | Assessments, strategy, enablement | Time-boxed, with the deliverable pack agreed up front. |
| Audit and roadmap | Before committing to a build | Short and fixed-scope, ending in a plan you own. |
| Outcome-based | Rare — objective measures only | Tied to an agreed metric. Proposed sparingly — few outcomes are cleanly attributable. |
No rate card here, and there will not be one — quoting before scope is guessing. Engagements start with a short paid discovery.
After the build
Pick one, and change your mind later if it stops fitting.
Keep it running. Dependency and SDK upgrades, security patching, crash triage, an agreed response time.
Keep it moving. Standing capacity against a jointly owned backlog, the same practice lead, the same shipped log.
Take it in-house. Documentation, the decision record, a recorded walkthrough, pairing with your engineers. No lock-in.
Handover is a real option, not a threat. Several arrangements we like best began as one.
Most people arrive with a symptom, not a spec. Thirty minutes usually finds the right practice — and whether we are the right people.
Book a 30-min scoping call