CRM and operations, connected.

Start with the workflow that needs to change

When enquiries, customer records and delivery tasks live in different places, the useful question is where the process breaks. We help you examine that workflow, choose an approach and implement the agreed scope.

This service suits teams with a recurring handoff to fix, a person responsible for the process and users who can help test the change. Bring the tools you use today and one recent example of a missed follow-up, duplicated record or unclear responsibility.

Choose the smallest change that solves it

The right project might be:

• Configuration and implementation: improve fields, permissions, views, stages or team workflows in your existing software. Native features can still require paid setup, data cleanup and training; a straightforward change your team can make itself may need no project.
• Integration: connect an existing CRM to another tool and define what happens when a transfer fails. See our automation and integration approach.
• A different existing product: compare its fit, migration work and ongoing cost before commissioning software.
• A custom system: build around a necessary workflow that the evaluated options cannot adequately support.

If Airtable is part of the decision, our Airtable versus custom CRM guide explains what to check before staying, extending or migrating.

What a first scope could look like

For example, start with the handoff from a qualified enquiry to an active client project. Agree which details are required, who owns each step, what each person can access and how the team knows work is ready to move forward.

A focused first release could include an agreed pipeline, customer records, assigned next actions and one necessary connection to another system. This is an example scope; the actual requirements come from your process.

We define acceptance checks with you, such as whether the right person can find a record, update its status and see the next action. Later phases can address other workflows once the first is working.

Plan for the people who will run it

Discovery covers existing data, access rules, integrations and the exceptions that a simple process diagram can miss. Where migration is needed, agree a trial, reconciliation checks and a recovery plan before switching the live workflow.

The delivery scope should also cover documentation, administrator access, team handover and ongoing support responsibilities.

For examples, explore the illustrative business-systems workflows. Our separate 21Goals product-engineering case study covers custom prediction logic, football-data integration and administration workflows in a different domain.

What determines price and timing?

The main factors are the workflow, number of user roles, condition of existing data, integrations and testing needed. Configuration, integration and custom development involve different amounts of work.

We establish the scope and assumptions before proposing a price or delivery schedule. Share any budget or deadline constraints early so the proposed first phase can reflect them.

Discuss one workflow

Tell us which tools you use, where work gets stuck and who is affected. We can discuss the options and what information is needed for a sensible next step. You do not need a finished technical specification.

Send the context for your CRM workflow or discuss it in a call.