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.
Service · Business systems
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
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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
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.
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.
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.
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
Several people edit the same files, nobody trusts the latest version and mistakes are found by customers rather than by the system.
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.
Your pricing method, scheduling logic or service model is a genuine advantage, and you would rather not mould it to a vendor’s defaults.
Alternatives
Organisation-wide platforms with complex governance, multiple business units and heavy audit needs suit our enterprise engagement better.
Open registerIf your existing products cover the work and the pain is re-keying between them, workflow automation may solve it without a new application.
Open registerInventory, procurement, accounting and manufacturing planning are usually better served by implementing and extending an ERP.
Open registerBespoke 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 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.
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.
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.
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
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.
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.
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.
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.
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.
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.
Related services
When partners, suppliers or other internal systems need a stable, documented interface into the new application.
Open registerReporting and dashboards built on the cleaner operational data the new system produces.
Open registerOngoing cover for fixes, security patches and small changes once the system is part of daily operations.
Open registerPrimary sources
Dated official documentation, standards, and research that support the factual claims on this page.
A framework of security requirements used to set and verify controls for web applications.
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
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.