Services / Custom software development
Custom software development.
When the requirements go beyond a single tool.
Problems this work can address
- A legacy system limits changes and connections to other software.
- Departments hold separate versions of customer, product or job records.
- Your requirements span customer accounts, staff tools and reporting.
- You need a development team to deliver a defined project or phased replacement.
Scope
What we can build with you.
We establish which parts are useful for your business and what your existing tools can already do before agreeing the build.
Business applications and databases
Software for the records, rules and processes specific to your business. We define the data model and permissions before building the application.Legacy system replacement
Review the existing functions, identify what needs to move and plan data migration. Where practical, release in stages so the team can keep working during the transition.Connected customer and staff applications
Websites, account areas and internal tools that share the appropriate information. Each user sees the functions and records they are authorised to access.Product planning and technical delivery
Help turn business requirements into a prioritised build plan. You have direct access to the project team, with agreed responsibilities and regular reviews.Testing and release planning
Test business rules, permissions and integrations against agreed acceptance criteria. Plan deployment, backups and recovery before the system becomes part of daily work.Code, documentation and ongoing support
Hand over source code, account access and maintenance instructions. We agree what your team will operate and where you want continued development or support.
In practice · Recruitment agency
Website, CRM and applications in one project.
Launched provided the recruitment agency’s technology and product team. The work covered CRM selection and migration, a website, Airtable, n8n automation, custom applications and sales dashboards.
Agree the whole project. Deliver it in useful stages.
Larger systems need explicit priorities and dependencies. We agree the first release, test it with users and review later phases as the requirements become clearer.
Scope
Review requirements, existing software and build-or-buy options.
Your involvement: Bring decision-makers, users and existing documentation.
Technical plan, release scope and budget
Build
Develop the application, integrations and migration tools.
Your involvement: Review progress and resolve business-rule questions.
Working releases for user review
Test
Test access, calculations, integrations and recovery steps.
Your involvement: Check tasks and migrated records against the agreed brief.
Acceptance checks and release plan
Launch
Deploy, migrate the agreed data and train the team.
Your involvement: Approve rollout and assign operational responsibility.
Live system, documentation and support
After launch
We agree launch aftercare, handover and any ongoing maintenance or development with you. Your organisation retains access to its code, accounts and documentation.
Support and ongoing developmentPlanning the work.
Start with the requirements and the systems already in place.
Should we build custom software or buy an existing product?
We assess existing products first. Custom development is useful when essential requirements cannot be met through configuration or sensible integrations. We compare the build and maintenance work with the limits and ongoing costs of the available products.
How are cost and timescale agreed?
Discovery defines the requirements, integrations, migration and acceptance criteria. We then quote the agreed scope or first phase, with a schedule and a process for handling changes. Larger projects may need several releases.
Can you work alongside our technical team?
Yes. We agree who owns architecture, development, testing and release decisions. Your team can review the work and take responsibility for parts of the system or its ongoing maintenance.
Who owns the code and accounts?
Your organisation receives the project source code, relevant account access and documentation. Third-party platforms and libraries retain their own licence terms, and their subscriptions are identified in the project scope.
How can we help you work better?
You don’t need a brief or a solution in mind. Tell us what’s proving difficult or what you’d like to improve. We’ll explore the options together and agree where to start.