Services
Software development from planning through handover.
We design and build new products, modernize existing platforms, and add AI features and integrations. Each engagement covers the technical approach, delivery stages, operational requirements, documentation, and ownership terms.
Dedicated service pages
Our engineers have built software at
What we usually walk into
- “The prototype worked. A real business depends on it now and we are afraid to touch it.”
- “We shipped quickly, and the person who wrote the login code has left the company.”
- “We have an AI feature that demos beautifully and nobody here trusts it.”
- “The last team delivered, invoiced, and disappeared. We cannot maintain what they left us.”
If one of those is your situation, this is the work that gets you out of it.
Zero to launch
A new product, from scratch.
Product planning, design, engineering, and launch support, with your team involved in the decisions that affect long-term ownership.
We begin by clarifying the users, business requirements, data, and technical constraints. From there, we define an initial release, test the riskiest assumptions, and refine the product with your team.
What you end up with
- A production release aligned with an agreed scope
- Documentation and a defined handover plan
- A client-owned source repository
Scale what works
Scale what already works.
A platform with real traction that needs more users, more markets, or more channels without downtime.
We review the application architecture, data layer, integrations, and operational history to identify current constraints. Changes are prioritized according to business impact, technical risk, and the need to keep the service available.
What you end up with
- A documented view of current performance constraints
- Prioritized improvements to reliability and capacity
- Monitoring and operational documentation for your team
AI inside
AI inside what you already run.
AI features added to existing software with defined use cases, evaluation criteria, permissions, and human review where appropriate.
We start with the decision or workflow the feature is intended to support. Evaluation, monitoring, access controls, and fallback behaviour are designed in proportion to the risk of an incorrect output.
What you end up with
- Documented evaluation criteria and test cases
- Cost, latency, and failure-mode monitoring
- Defined permissions, fallbacks, and review points
What we can build for you.
Software, mobile, AI, integrations, and the reporting that has to sit under all of it. Most engagements use three or four of these at once.
Web platforms
The product your customers log into, and the admin tools your own team needs behind it.
Customer portals / Dashboards / Marketplaces / Admin and back office
Service pageMobile apps
Cross platform or installable web, chosen for what the product has to do rather than what is fashionable.
iOS and Android / Progressive web apps / Offline and sync / Push and notifications
Service pageAI features
AI features with defined evaluation criteria, monitoring, and human review for higher-risk decisions.
Assistants and chat / Document extraction / Classification and scoring / Search and recommendations
Service pageAPIs and integrations
Connecting the systems that never quite agree with each other, without losing data in the gap.
Payments and payroll / CRM and support tools / Public APIs and webhooks / Legacy system bridges
Service pageData and reporting
Getting the numbers out of the product and in front of the people who make decisions on them.
Pipelines and warehousing / Reporting dashboards / Event tracking / Exports and audit trails
Service pageAutomation and internal tools
The manual process somebody is currently doing in a spreadsheet at the end of every month.
Workflow automation / Approvals and queues / Scheduled jobs / Ops tooling
Service pageIndustries we have shipped in
Careers and hiring. Marketing and content. HR and payroll. Cross border payments.
Those are the four we have built, launched, and still run day to day. Payroll and payments in particular come with rules you cannot talk your way around, which is where most of our habits about access control and audit logs came from. We take work outside these areas, and when a domain is genuinely new to us we say so before you sign anything.
Built quickly, and built to survive production.
Our delivery process addresses architecture, permissions, dependencies, monitoring, and maintainability alongside feature development.
Permissions before features
Roles, permissions, and sensitive data paths are defined early and reviewed as the product changes.
Secrets, data separation, audit logs
Secrets are kept outside the source repository. Data isolation and audit requirements are defined according to the product and its users.
The stack is chosen for the product
Technology choices account for expected load, regulatory or contractual requirements, and the team responsible for ongoing maintenance.
Engineering review
Code changes are reviewed before release. Dependencies, database changes, access controls, and generated code receive additional scrutiny where needed.
AI is a tool we use when it earns its place. We recommend AI only when it is appropriate to the use case, operating requirements, and expected value.
A four-phase delivery process.
Each phase has a defined output and a decision point before the next stage begins.
Phase 01
Define the problem
We review the users, workflow, data, constraints, and expected outcome before defining the initial scope.
Deliverable: A scoped plan, initial technical approach, and identified risks.
Decision: Proceed, revise the scope, or conduct further discovery.
Phase 02
Validate the approach
We test the assumptions that carry the most product or technical risk before expanding the build.
Deliverable: A prototype or technical validation and an agreed baseline.
Decision: Continue, adjust the approach, or reconsider the scope.
Phase 03
Build it and monitor it
Work is released in reviewable increments. Monitoring, access controls, and operational requirements are added as the system develops.
Deliverable: A production release, monitoring, operating documentation, and security review.
Decision: Release, limit availability, or complete additional work.
Phase 04
Handover and support
We complete the agreed documentation and knowledge transfer, then provide ongoing support if the engagement includes it.
Deliverable: Repository access, architecture documentation, and an agreed support plan.
Decision: Transition to your team or continue with defined support.
Timing depends on scope, existing systems, integrations, and review requirements. We provide a delivery estimate after the initial assessment. We limit the number of concurrent engagements so the proposed team can remain involved throughout delivery.
Engagement fit.
These criteria help determine whether our delivery model is appropriate for the work.
Work we do well
- A product that has to exist in months, with a team that will keep running it
- Software where being wrong is expensive and quality has to be measured
- A prototype that got traction and now has to be rebuilt properly
- Existing software that works but nobody enjoys using
- A founding team that wants to sit in the build
A poor fit
- Large-scale staffing requirements or interchangeable contractor teams
- Projects without a defined business problem or accountable product owner
- Fixed scope written before anyone has spoken to a user
- A request for a large interchangeable bench
Tell us the problem you're trying to solve.
Share the business problem, current system, and timing. An initial specification is helpful but not required. We aim to respond within two working days.