Premium tools
Software your team prefers over every spreadsheet and workaround.
Service 03 of 15
Custom software development
Software, ERPs and internal tools built around how your business works.
- Typical timeline
- 10–24 weeks
- Pricing
- Fixed quote
- Team
- Product lead + 2–4 engineers
Our 3 promises
Your process. Our goal.
Three promises we make on every custom build.
Fits like a glove
Built around how you really work, not how a template says you should.
Built to last
Clean, documented code any developer can pick up for years.
Tech stack
The stack behind your custom software development
Proven, well-supported tools at every layer. Picked for your product, never for our habits.
- Interface.NET Blazor
- InterfaceMost requestedReact
- BackendPython
- InterfaceMost requestedTypeScript
- Backend.NET
- DataSQL Server
- BackendMost requestedNode.js
- DataRedis
- DataMost requestedPostgreSQL
- CloudAWS
- CloudDocker
- CloudMost requestedAzure
- QualityCode review
- QualityMost requestedAutomated tests
- QualitySentry
What’s included
What you get
Everything in scope, from first workshop to launch.
01StartProcess mapping
We sit with your team and map how work really happens.
Read more +Show less −
Process mapping is a 1–3 week phase where we sit with your team and document how work actually gets done today, including the spreadsheets and workarounds. It shows where software will save the most time. You receive written workflow maps and a fixed, itemised quote before any build starts.
What you get
- Workflow maps of each process in scope
- List of pain points, delays and manual steps
- Inventory of current systems, spreadsheets and data sources
- Prioritised list of what to build first
- Fixed, itemised quote and delivery timeline
How it works
- Interview and shadow the people who do the work
- Map each process step by step, including exceptions
- Agree priorities and scope with you
- Present the process map and fixed quote for approval
Good to know: Give us time with front-line staff, not only managers, as they know where the real workarounds are.
02PlanSystem design
Architecture, data model and integrations, agreed up front.
Read more +Show less −
System design sets out how the software will be built before coding starts: its architecture, how data is stored and how it connects to your other systems. You get a written design you can review and question. Agreeing this up front avoids costly changes halfway through the build.
What you get
- Architecture overview in plain English with diagrams
- Data model showing what is stored and how it relates
- Integration plan for each existing system
- User roles and permission rules
- Hosting, security and backup approach, including UK or EU hosting
How it works
- Turn the process maps into system requirements
- Design architecture, data model and integrations
- Review the design with you and your IT contact
- Sign off before the first build sprint
Good to know: If you have an IT provider or in-house IT person, involve them at this stage so hosting and access fit your setup.
03BuildBuild
Internal tools, ERPs, CRMs and automations.
Read more +Show less −
The build stage develops your internal tool, ERP, CRM or automation in two-week sprints, with a working demo at the end of each one. We use proven tools such as React, .NET, Node.js and PostgreSQL. Your team can try each part as it is built, so feedback shapes the next sprint.
What you get
- Working software released in stages every sprint
- Role-based access so staff see only what they need
- Reports and dashboards for the figures you track
- Automations that replace manual and repeated tasks
- Automated tests and code review on every change
- Source code in a repository you own
How it works
- Plan each sprint from the agreed priorities
- Build, test and review features
- Demo working software to you every two weeks
- Adjust the next sprint based on your feedback
Good to know: Name one person on your side who can make quick decisions, as waiting for answers is the most common cause of delay.
04LaunchData migration
Move data safely from old systems and spreadsheets.
Read more +Show less −
Data migration moves your records from old systems and spreadsheets into the new software without losing or corrupting anything. We clean and test the data in trial runs before the final move. Most migrations end with a planned cut-over, often over a weekend, so daily work is not disrupted.
What you get
- Audit of current data and its quality
- Clean-up of duplicates, gaps and inconsistent formats
- Mapping of every old field to the new system
- Trial migrations with checked record counts and totals
- Final migration with a sign-off report
- Rollback plan if anything does not match
How it works
- Export and review data from each source
- Clean and map data to the new structure
- Run trial migrations and check results with you
- Carry out the final migration at an agreed time
Good to know: Decide early which old records you actually need, as moving years of unused data adds time and cost.
05LaunchTraining & handover
Guides and training so your team can run it.
Read more +Show less −
Training and handover makes sure your team can use and run the new system confidently from the day it goes live. We run sessions for each type of user and leave written guides behind. You also receive full technical documentation, so you are never tied to us.
What you get
- Training sessions for each user role, in person or online
- Step-by-step user guides with screenshots
- Admin guide for managing users and settings
- Technical documentation for any future developer
- Handover of all code, accounts and credentials
- Support period after go-live for questions and fixes
How it works
- Plan training around your team's schedules
- Run sessions on a test copy of the system
- Hand over guides, documentation and access
- Support your team through the first weeks live
Good to know: Choose one or two internal champions to train first, as staff often ask colleagues before they ask us.
How it works
From idea to launch
Every service runs through the same five steps. Here is what each one means for Custom software development.
01of 05
UnderstandWeeks 1–3Once
We map how your business works today and where software can save time.
You getProcess map
What we do
- Workshops with the people who will use it
- Map current processes, tools and data
- Find the steps worth automating first
You get
- Process map
- Requirements document
- Priority feature list
From you
- Time with key staff
- Access to current systems and data
Tools
- Miro
- Notion
02of 05
PlanBefore any codeOnce
Architecture, data model and a fixed quote you approve.
You getFixed quote & timeline
What we do
- Wireframes for key screens
- Data model and integration plan
- Migration and rollout plan
You get
- Fixed, itemised quote
- Timeline with milestones
- Architecture overview
From you
- Review and approve the plan
Tools
- Figma
- Jira
03of 05
BuildTwo-week sprints↻ Repeats
The system built in sprints, with a working demo every two weeks.
You getWorking demo every sprint
What we do
- Core modules, roles and permissions
- Integrations with your existing tools
- Code review and automated tests on every change
You get
- A working demo every two weeks
- Shared sprint board
- Access to your code repository
From you
- 30-minute demo every two weeks
- Feedback within 3 working days
Tools
- .NET / Node.js
- PostgreSQL
- GitHub
04of 05
Test & launchEach release↻ Repeats
Testing, data migration and staff training before go-live.
You getLive system
What we do
- Testing with real data and real users
- Data migration from old systems
- Staff training and rollout
You get
- Live system
- Migration and test report
- User guides and handover documents
From you
- User acceptance testing
- Go-live sign-off
Tools
- Playwright
- Azure / AWS
05of 05
Support & growAfter launch↻ Repeats
Maintenance, fixes and new modules as your business changes.
You getOngoing improvements
What we do
- Monitoring, fixes and updates
- New modules and reports
- Monthly review of usage and priorities
You get
- Monthly update
- Uptime and error reports
From you
- Monthly 30-minute review
Tools
- Sentry
- Grafana
FAQ
Custom software development questions
What is bespoke software?
Software designed and built for one organisation's processes, rather than an off-the-shelf product. You control the features, data and roadmap, with no per-seat licence fees.
How much does bespoke software cost?
UK projects typically range from £10,000 for a simple internal tool to £150,000+ for larger systems. We fix the price for an agreed scope after discovery.
How long does it take?
Most of our custom software projects take 10–24 weeks, delivered in two-week sprints so you can use parts of the system early.
Bespoke or off-the-shelf: which is better?
Off-the-shelf suits standard processes. Bespoke pays off when your workflow is a competitive advantage, licences are costly, or several tools need joining up.
Can you integrate with our existing systems?
Yes. We connect to CRMs, ERPs, accounting tools like Xero and Sage, and legacy databases through APIs or secure data syncs.
Who owns the software?
You do. All IP is assigned to you in the contract, and the code is in your repository from the first sprint.
Let’s talk
Let’s talk
A 30-minute call with an engineer and a clear next step for your project.