CRM
Relationships, opportunities and commercial activity
Business software shaped around your operation.
We build and extend business applications around the records, decisions and handoffs your teams manage. Our experience includes practice management, fleet and transportation, contracts, equipment registers, ERP and CRM systems. An engagement can deliver one focused workflow, an integration or a new application, with ownership and operating rules agreed for the actual organisation.
Different operations, specific responsibilities
Explore the contexts we have worked in. Each connects different records and decisions.
Practice management
Scheduling, cases, documents and billing involve separate states and roles. A booking does not prove completed work or readiness for billing. Connect the supporting records and next responsible person.
A first scope can join scheduling to case/document context and a defined billing handoff. Agree completion rules, restricted information and access requirements for the actual practice.
- ScheduleBooking and responsible people
- Case and documentsSupporting work and completion state
- Billing handoffAgreed readiness and restricted information
Fleet and transportation
Connect vehicles, assignments, journeys and maintenance. A vehicle appearing available in a schedule may still be restricted from an assignment.
Retain earlier plans when reallocating work, distinguish planned, underway and completed activity, and preserve the history behind conflicts and decisions. Agree the source of states used by scheduling, finance and reporting.
- VehicleAvailability and restrictions
- Assignment and journeyPlanned, underway or completed work
- Maintenance and historyConflicts, reallocation and retained decisions
Contracts and obligations
Keep approved versions, amendments and renewal proposals distinct. Identify the effective document and whether a change replaces a term, adds an obligation or remains proposed.
Connect approvals, supporting documents, renewal dates and obligations to responsible owners. Useful reminders lead to a defined action; access and changes remain in the same record context.
- Effective versionApproved terms and amendments
- ObligationDates, evidence and responsible owner
- Renewal proposalSeparate from the current agreement
Equipment custody and condition
Location, custody, inspection and maintenance answer different questions. Retain dated transfers and service events so current condition and responsibility can be explained.
A transfer does not change asset identity or remove maintenance obligations. Stable identifiers and reviewed imports/corrections prevent ambiguous records or duplicate assets.
- Asset identityStable register identifier
- Custody and locationDated transfer and responsible person
- Condition and serviceInspections and maintenance obligations
ERP responsibilities
Purchasing, stock, sales and finance can share master data while owning different decisions. Access to a common record does not grant authority for every action.
Extend a platform or build a focused application around explicit ownership of customers, products and transactions. Agree interface rejection, freshness and reconciliation instead of duplicating authoritative records unnecessarily.
- Master dataCustomer and product identities
- Operational transactionPurchasing, stock, sales and finance
- Authorised actionAgreed interfaces and decision ownership
CRM and the next handoff
Contacts, opportunities and accepted orders describe different stages. Retain activities, permissions and history as commercial responsibility passes to delivery and finance.
A portal and internal view need compatible meanings. A shared customer record may still require a distinct accounting account or contractual identity at the next handoff.
- Customer activityContacts, opportunities and history
- Accepted orderCommercial responsibility and agreement
- Delivery and financeCompatible meanings and mapped identities
These are operating contexts we have worked in, rather than one interchangeable application template. The actual organisation sets its rules, access and responsibilities.
Connect commercial and operational work
CRM and ERP can share a handoff while retaining distinct records and decision authority. Agree the order and customer mapping before duplicating authoritative data.
Agreed order and customer mapping
ERP
Purchasing, stock, sales and finance responsibilities
Buy, configure or build around the gap
Assess one workflow’s people, records, decisions and exceptions. A market product, configuration or integration may close the gap; custom work should take on a named responsibility that remains unsupported.
Account for ongoing cost and ownership. Configuration changes affect imports, approval rules and reports as well as forms; custom applications need explicit records, interfaces and operating actions.
Handover includes tested behaviour, integrations and operating context, whether the first delivery is a new application or an extension around existing tools.