Software development
Web platforms and internal tools built around how your business works, released in small, tested increments.
feat(booking): hold a slot for 10 minutes during checkout
by tech lead · +214 −38 · 9 files
What we build
Custom software solutions
We design, build and run web platforms, SaaS products and internal tools around how your business works, released in small, tested increments.
Customer portals
Self-service accounts, orders, bookings and documents, connected to your back-office systems.
Internal tools
Operations, case management and back-office apps that replace spreadsheets and email chains.
SaaS products
Multi-tenant products with subscriptions, roles and permissions, built to scale with customers.
Workflow and approvals
Rules-based workflows with audit trails, notifications and integrations.
Marketplaces and booking platforms
Multi-sided platforms with listings, bookings, payments and reviews.
Enterprise application extensions
Custom modules and apps that extend the ERP and CRM systems you run.
How to get started
Three steps to a plan for software development
- 1Tell us what you needUse the project form or book a call. A few sentences about the goal is enough to start.
- 2Free technical consultationWe go through your goals, users, existing systems and constraints with you.
- 3Your planA detailed plan covering the right tech stack, architecture, timeline and budget. Then you decide.
How it works
Architecture, chosen for your system
We structure each application to fit: a modular monolith, microservices, event-driven services or serverless functions. Switch to see what a change to payments redeploys.
deployable: app
One deployable, divided into modules with clear boundaries. The usual starting point: simple to run, easy to split later.
Deployable units
1
A payments change redeploys
the application, once
From commit to production
Every commit to main runs the same pipeline. Run it, or break a test to see it stop before anything ships.
lint
Waiting…
Every commit to main runs this pipeline. Choose a job to read its log.
Services
Software development services
Take one on its own, or combine them in one engagement with one team.
Discovery and architecture
A prioritized backlog, the architecture and a delivery plan before the build starts.
Full-cycle development
Design, build, testing and release in two-week sprints, with a demo of working software each time.
Dedicated teams
A cross-functional team working through your roadmap, alongside your own developers if you have them.
Support and maintenance
Monitoring, fixes, updates and improvements after launch.
Our approach
How the work runs
Each stage hands its output to the next, like the stages of a delivery pipeline.
- Stage 1
Discovery
Users, journeys, a prioritized backlog and an architecture decision record for the key choices.
- Stage 2
Foundations
Repository, CI/CDContinuous integration and continuous delivery: every change is built, tested and made ready to release automatically. pipeline, environments, infrastructure as codeServers, networks and services defined in files such as Terraform, so environments are repeatable and reviewed like code. and monitoring from day one.
- Stage 3
Sprints
Two-week sprints with code review, automated tests and a demo of working software.
- Stage 4
Release
Automated deployments, feature flagsSwitches that turn a feature on or off for some or all users without deploying new code. and a staged rollout to real users.
- Stage 5
Operate
Monitoring, alerts, service level objectives and a backlog of improvements.
What we'll need from you
Having these ready keeps the work moving.
A product owner
One person who prioritizes the backlog and accepts finished work.
Access to users
A few users for interviews and testing at key points.
System access
API access and test accounts for the systems it connects to.
Cloud and code accounts
Your cloud subscription and repository, so everything is in your name.
Who's on the project
Our team, working with product owner from yours.
Tech lead · our team · Owns architecture, code quality and technical decisions.
Deliverables
What you receive
Everything is handed over in your name: code, accounts and documentation.
Source code in your repository, with a documented architecture
What the documentation looks like
Every project ends with documents your team can run with. Here is an excerpt of one of them.
ADR 007: Start as a modular monolith
Status: accepted · decided in discovery
Context
One team of six, a first release in 12 weeks, and three clear business areas: orders, billing and accounts.
Decision
One deployable application with a module per business area, each owning its tables. Modules talk through interfaces, never each other's tables.
Consequences
Simple deployment and testing now. Billing can be extracted into a service later if it needs to scale on its own.
Measuring success
How success is measured
What we report on in software development projects. Which measures apply, and their targets, are agreed with you at the start.
Deployment frequency: How often changes reach production; frequent, small releases are safer than rare, large ones.
Reliability as a number
We agree a service level objective with you; the error budget is the downtime it allows. Choose an objective and see the policy change.
Availability objective for the application
Allowed downtime in 30 days: 43 minutes
Healthy
25 minutes left
Ship features as normal. The budget is there to spend on releasing faster.
Agreeing the objective and the policy up front turns reliability from an argument into a rule.
Readiness check
Are you ready for
software development?
Five questions, about a minute. You'll see what to settle first and a sensible starting point.
? Is there a clear problem and a group of users who have it? (y / n / ?)
How to start
From first call to production
Start where you are. Each step ends with a decision, so you commit to the next one only when it makes sense.
git show v0.1
Free technical consultation
Talk through the goal, the users, the systems involved and any deadlines.
- + A clear view of scope and priorities
- + A recommended next step
- + A plan covering stack, architecture, timeline and budget
Estimate the value
What it could be worth to you
Enter your own figures. The formula is shown, and the estimate can go with your enquiry.
# Time saved by replacing manual work
# formula: People × weekly hours × share automated × hourly cost × 52
Build or buy
When you don't need
a custom build
Part of the free technical consultation: when an existing product covers the need, we recommend it instead of a custom build. These are the options we weigh, alongside the tools you already have.
Technologies and standards
Chosen for your project
The main back-end ecosystems we build on. Choose one to see its frameworks and where it is strongest.
Frameworks
Node.js with NestJS or Fastify; React or Next.js on the front end
Strongest for
One language across front and back end; fast product teams; huge package ecosystem.
We recommend the stack that fits your team and systems, not a favourite.
Our technology radar for software development
techniques / adopt
Trunk-based development
Short-lived branches merged to main at least daily, so changes reach production in small, low-risk steps.
Our default. We use it on client projects unless there's a reason not to.
Our recommendations. Updated September 2026.
Front end
- React
- Next.js
- TypeScript
- Angular
- Vue
Back end
- Node.js
- .NET
- Java (Spring Boot)
- Python (Django, FastAPI)
- PostgreSQL
Delivery
- GitHub Actions
- Docker
- Kubernetes
- Terraform
Built to
- OWASP Top 10:2025
- OWASP ASVS 5.0
- WCAG 2.2 AA
- Twelve-Factor App
In your industry
Where it applies
What this work delivers in the industries we serve.
HealthcareTelehealthVideo visits with scheduling, virtual waiting rooms and visit notes, connected to your calendar and records.
Non-ProfitsProgram and case managementTools for recording beneficiaries, services delivered and outcomes, replacing paper forms and spreadsheets.
Real EstateTenant and owner portalsOnline rent payment, maintenance requests with photos, lease documents and owner statements.
EducationAdmissions and enrollment portalsOnline applications, document upload, fee payment and decision tracking, connected to your SIS and CRM.
Questions
Common questions
about software development
Who owns the code?
You do. Code lives in your repository and cloud accounts from the first commit, and the handover includes documentation, runbooks and access.
Can you work with our in-house developers?
Yes. We can work in your repositories and ceremonies, pair with your developers and hand over gradually as your team takes ownership.
How do you keep quality up while moving fast?
Code review on every change, automated tests in the pipeline, and small, frequent releases that are easy to roll back.
How is a project priced?
Well-defined scopes are delivered as fixed-price engagements; when requirements are still evolving, we provide a dedicated team instead. Either way, the free technical consultation ends with a plan covering tech stack, architecture, timeline and budget, so you know the cost before work starts.
More in Custom Software Development
How it connects
- Pairs withQuality assuranceAutomated testing in the pipeline keeps frequent releases safe.
- Relies onAPI development & integrationMost products depend on APIs to talk to your other systems.
- Pairs withMobile app developmentThe same backend and APIs can serve web and mobile apps.
Planning software development work?
Start with a free technical consultation: a detailed plan covering the right tech stack, architecture, timeline and budget for your project.
Start a project