Skip to content

Service · Business systems

Custom Software Development

Commission software for a workflow that spreadsheets, shared inboxes and packaged tools no longer carry: quoting, scheduling, compliance tracking, job management or whatever process your business actually runs on. We map the process with the people who do it, check whether something off the shelf would serve, and only then design, build and roll out a system that fits.

Build-versus-buy check before any custom scope

Integrations with the finance, CRM and identity tools you keep

Data migration and cutover planned as part of delivery

Deliverables

What a custom software development engagement delivers.

01Delivered

Process map and build-versus-buy note

A diagram of the current workflow with its records, approvals, hand-offs and workarounds, plus a frank note on which parts packaged software could cover and which genuinely need bespoke code.

02Delivered

The application itself

A web application, and mobile companion where field staff need one, encoding your business rules, roles, approvals, task queues and notifications, with an audit trail for every consequential change.

03Delivered

Integration adapters

Connections to the accounting package, CRM, identity provider, document storage or partner systems you keep, each with defined ownership of data, retry behaviour and a way to reconcile mismatches.

04Delivered

Migration of existing records

Scripts that clean, map and import data from spreadsheets or the system being retired, rehearsed against copies of production data until the counts and spot checks agree.

05Delivered

Rollout material

Role-based training guides, an administrator handbook, support procedures for the first live period and a plan for switching off the tools the new system replaces.

Early decisions

Technical decisions we settle early in custom software development.

01Decided

Buy, configure or build

If a configurable product covers most of the workflow, extending it is usually cheaper to own. We make that call per module, and sometimes the right answer is a small custom layer around a packaged core.

02Decided

The system of record for each entity

Customers might live in the CRM, invoices in accounting and jobs in the new system. Deciding which system owns each record, and which only mirrors it, prevents duplicate truth and reconciliation headaches.

03Decided

How rules are expressed

Approval thresholds, pricing tables and eligibility checks change. We separate rules that administrators should edit from rules that belong in code, so routine policy changes do not need a developer.

04Decided

Sign-in and permissions

Staff usually sign in through Microsoft Entra ID, Google Workspace or another existing directory. We map job roles to permissions and decide how contractors and external partners are admitted.

05Decided

Cutover style

A single switch-over date, a team-by-team migration or a period of running both systems side by side each carry different risk and training load. The choice shapes migration tooling and support planning.

06Decided

Hosting and data residency

Where the system runs, which region holds the data and who administers backups follow from your contracts and regulatory duties, and are agreed before infrastructure is provisioned.

Engagement

How a custom software development engagement runs.

  1. 01Phase 1

    Shadow the work

    We sit with the people who run the process, collect real examples of the forms, spreadsheets and emails involved, and write down every exception they handle by hand.

  2. 02Phase 2

    Agree the model and the boundaries

    Entities, states, roles and integrations are drafted, reviewed with process owners and fixed in a scope that names what the first release replaces and what stays where it is.

  3. 03Phase 3

    Build in usable increments

    Each increment delivers a working slice that a small group of real users tries on realistic data, so feedback arrives while changes are still inexpensive.

  4. 04Phase 4

    Migrate, switch over and retire

    Data is migrated in rehearsal and then for real, staff are trained, the old tools are made read-only or switched off, and the codebase passes to your team or a support arrangement.

Fit

When custom software is the right choice.

01Good fit

A process has outgrown its spreadsheet

Several people edit the same files, nobody trusts the latest version and mistakes are found by customers rather than by the system.

02Good fit

Packaged tools force awkward workarounds

You have tried the obvious products and your team still re-keys data between them or keeps side spreadsheets to cover what they cannot do.

03Good fit

The process is how you compete

Your pricing method, scheduling logic or service model is a genuine advantage, and you would rather not mould it to a vendor’s defaults.

Start by questioning whether to build

Bespoke software carries a lifetime cost: hosting, security updates, staff who understand it. That cost is worth paying only where packaged products genuinely cannot do the job or would force you to abandon a way of working that makes you money. So the first deliverable is an honest build-versus-buy view, module by module.

Often the answer is mixed. Accounting stays in the product you already use, identity stays in your directory, and the custom application handles the specific workflow that nothing else fits, exchanging data with the rest through well-defined adapters.

The workarounds are the requirements

The most valuable discovery material is rarely the official process document. It is the colour-coded spreadsheet column, the sticky note on a monitor, the email someone forwards every Friday. Each workaround marks a rule the current tools cannot express. We collect them deliberately and turn them into states, validations and notifications, so the new system absorbs the knowledge instead of losing it.

Integration and data deserve their own plan

Internal systems fail less often on screens than on data. Duplicate customers, free-text dates and records that exist in two places with different values will all surface during migration. We profile the source data early, agree cleaning rules with the people who own it and rehearse the import repeatedly, so the live cutover is the dullest day of the project.

Each integration gets a written contract covering which side owns a field, what happens when the other system is unavailable and how discrepancies are reported to a person who can fix them.

Adoption is part of delivery

Software that staff avoid is a sunk cost. We involve future users in every increment, keep the language on screen consistent with how they already talk about the work and plan training by role. Retiring the old spreadsheet or tool is written into the rollout, because systems that run in parallel indefinitely leave nobody sure which one is right.

Keeping it maintainable after we leave

Business systems live for years and change hands. We favour widely used frameworks, keep business rules readable in one place, write tests around the calculations that matter and document why each integration behaves as it does. Your own developers, a new supplier or our support team should all be able to pick it up without archaeology.

FAQ

Questions to resolve before the build.

01What pushes the cost of custom business software up or down?

The number of distinct roles and approval paths, how many systems it must integrate with, the condition of the data being migrated, reporting needs, and whether staff need offline or mobile access. Integrations and migration are frequently underestimated, so we estimate them separately from screens and features.

02What decides how long it takes to replace our current process?

Availability of the people who know the process is often the limiting factor, followed by integration access, data quality and how the cutover is staged. A phased rollout takes longer overall but reduces disruption, so we discuss the trade-off with you before fixing a plan.

03What exactly do we receive when the project closes?

Source code, infrastructure definitions, database schema documentation, integration notes, migration scripts and logs, administrator and user guides, and a list of known limitations. Credentials and cloud accounts are already in your organisation’s name.

04Does the business own the software and the data?

Yes. Code written for you is assigned to you, the data stays in infrastructure you control, and any open-source components are listed with their licences so your legal team can review them.

05How is the system accepted before staff rely on it?

Process owners approve written scenarios drawn from real cases, including the awkward exceptions, on a staging environment populated with migrated data. Migration is accepted separately against agreed record counts and sample checks.

06What is not included in a custom software project?

Licences for third-party software, changes to your other vendors’ systems, organisational redesign and long-term hosting fees sit outside the build. Process changes that the new software enables still need a sponsor inside your business to lead them.

Primary sources

References behind this page

Dated official documentation, standards, and research that support the factual claims on this page.

  1. 01
    OWASP Application Security Verification Standard

    A framework of security requirements used to set and verify controls for web applications.

  2. 02
    Microsoft Entra ID documentation

    Single sign-on and directory integration for staff-facing business applications.

How to read this page

Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.

Next decision

Turn the brief into an accepted product scope.

Define outcomes, constraints, evidence, rights and handover before delivery begins.

Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.