Custom CRMs built around the people doing the work.
A practical approach to customer records, enquiries, ownership and follow-up. The NxtGen Trophies CRM provides a working example of translating a business’s requirements into a shared operational system.
SystemsWebsitesStrategy
NxtGen CRM
Implementation
Manual first
Core approach
Desktop + mobile web
Access
The brief
The brief
NxtGen needed its directors to keep organisation details, enquiries and next actions together. The starting requirement was a manual-first system that supported their actual business-development work, with a clear person responsible for each enquiry.
The system needed enough structure for one director to understand another’s work, while keeping everyday entry straightforward. Adding fields or automation was only useful when it supported a real task.
Our role
Our role
Saxon Bridge shaped the records, interface and workflow around the directors’ requirements, then refined the system as those requirements developed. NxtGen is a partner venture in which Charlie is a director; it is the implementation evidence for this case study, rather than a separate independent client commission.
How the work operated
How the work operated
The workflow was organised around an organisation record, the associated enquiry, its requirements, the person responsible and a dated next action. This gives a handover a useful starting point: what is known, what is missing and what should happen next.
What we delivered
Built
Organisation and customer records
Enquiry requirements and ownership
Activity, tasks and next actions
Responsive mobile web-app access
Produced
A shared customer and enquiry interface
A practical handover structure
Public-safe interface examples using fictional records
Operated
CRM use by the NxtGen directors for business development
Iterative refinement from operator requirements
Continuing development of quotation and email workflows
Inside the CRM
Customer context, responsibility and the next action.
The public website and the internal CRM perform different jobs. The website explains the NxtGen offer and gives customers a route to enquire. The CRM helps the directors organise the information and follow-up once work is being handled internally. The evidence below does not imply an automatic website-to-CRM transfer.
01 · CUSTOMER CONTEXT
Prepare the next conversation from the organisation record.
The fictional Demo Club A record holds the organisation type, activity, adult contact, explanatory note and dated next action. A director can inspect the relationship context before contacting the club, rather than relying on a separate spreadsheet row or inbox thread.
Actual NxtGen CRM interface with fictional demonstration data. The record presents the organisation, an adult contact and the next action together.
02 · REQUIREMENTS
Keep what is known—and what is still missing—with the enquiry.
The enquiry records the occasion, requested personalisation and relevant dates while leaving quantities visibly unconfirmed. It gives the director enough context to ask the next question without presenting the fictional request as a completed quotation.
Actual interface with fictional demonstration data. The requirements and unresolved details remain attached to the enquiry.
03 · RESPONSIBILITY
Make the owner and dated next action visible.
The organisations view shows Demo Director B as owner and the action to confirm quantities and the engraving deadline. That presentation supports an intended handover: another director can inspect the task and linked context. The static evidence does not prove concurrent use or permission enforcement.
Actual interface with fictional demonstration data. Responsibility and the dated follow-up are visible at organisation level.
A genuine responsive capture at a 390 × 844 CSS-pixel viewport, using fictional demonstration data.
04 · EVERYDAY ACCESS
Review the task through the mobile web app.
The task view keeps the action, due date, priority, linked enquiry and note readable at a mobile viewport. It supports useful browser access with a network connection. It is not evidence of a native application, offline operation or every CRM function being available on a phone.
Development status: organisation records, enquiry presentation, ownership, activity, tasks and responsive mobile web-app access are evidenced in the current interface. Quotation and email/correspondence workflows remain in development unless separately established by current production evidence. Automatic website import, payment, stock and accounting workflows are not claimed.
These describe implementation scope, not measured revenue, conversion or time savings.
Outcome
A useful CRM makes the customer context, responsibility and next action easy to find. Its structure should follow the business workflow and develop with the people using it.
