- Challenge
- We need a service built and don’t have the people. That was how the client put it on the first call.
- Approach
- We built the service with the client’s product team, took it through load and security testing, and handed over the code with its runbook.
- Stack
- TypeScript · PostgreSQL · REST API · Cloudflare Workers
- Result
- The service is live, and the client’s own developers now maintain it.
Software development
Web apps, APIs and backend services, built by engineers who also run them.
Talk to an engineerWhat we do
Software development consultancy
An assessment of your Software development setup, with findings ranked by risk and effort.
Software development delivery
We design and build it with your team, in your accounts, documented as we go.
Software development support
Monitoring, patching and upgrades, with incident response agreed per contract.
Software development training
Workshops and pairing on Software development, built around your own systems.
Tools we work with
Languages & frameworks
- TypeScript
- Node.js
- .NET
- C#
- ASP.NET Core
- Go
- Python
- Next.js
- React
- FastAPI
APIs & integration
- REST
- GraphQL
- gRPC
- OpenAPI
- webhooks
- Stripe
- Kafka
- RabbitMQ
Edge & serverless
- Cloudflare Workers
- AWS Lambda
- Azure Functions
- Cloud Run
Data
- PostgreSQL
- MySQL
- Microsoft SQL Server
- Redis
- DynamoDB
- Entity Framework Core
- Prisma
- Drizzle
Web servers
- NGINX
- Apache HTTP Server
- IIS
- Caddy
- Traefik
- Kestrel
Testing & quality
- Vitest
- Jest
- Playwright
- pytest
- k6
- ESLint
How an engagement runs
- 1 A call. 30 minutes with an engineer to understand the problem.
- 2 A look. Read-only access or a walkthrough, so we scope from facts.
- 3 A proposal. Scope, deliverables and a price model: fixed scope, day rate or retainer.
- 4 The work. In your accounts and repositories, alongside your team.
- 5 A handover. Documentation and a session with your team, so you’re not dependent on us.
Proof
A recent Software development engagement. We keep client names private, but the problem, the work and the outcome are exactly as they happened.
See our workQuestions
Do you work in our accounts or yours?
Yours. Everything we build lives in your cloud accounts and repositories from day one, so there is nothing to migrate when we finish.
Can you work alongside our own team?
Yes, and we prefer it. We can run a project ourselves, embed engineers in your team, or pair with your people so they pick it up as we go.
How is this priced?
Depending on the work: a fixed-scope price, a day rate or a monthly retainer. We agree it in a written proposal before anything starts.