Enquiries live in separate places
Spreadsheets, inboxes and message histories give different people different views of the same enquiry. Important context becomes difficult to retrieve.
Custom CRM & Business Systems / Mates Creation
Keep every lead, follow-up and customer record in view.
When enquiries are spread across spreadsheets, inboxes and messages, your team can lose track of ownership and the next follow-up. A customer relationship management system, or CRM, brings those records into one agreed workflow. We discuss custom lead management, sales dashboards and internal admin tools for property consultants, service teams and growing businesses. We first assess whether your existing CRM can be configured or connected before recommending a custom build.
Discuss Your Project See what can be includedWhere the work begins
A lead needs an owner and a next action.
Follow-ups are easy to miss
When ownership and due dates are unclear, a promising enquiry can sit unattended. The team needs a shared record of who should act next.
The existing tool does not fit
A standard system may lack the fields or stages your process needs. Review whether configuration can close that gap before committing to custom development.
Our approach
Model the sales process before building the screens.
We review your lead sources, stages and follow-up responsibilities with the people using the system. That produces an agreed record structure, user roles and a first-release plan. The work can cover customer screens, pipeline actions, reminders and dashboards, with integrations assessed individually. We check sample records and permission behaviour before handover, then explain how the team manages users and everyday information.
Talk through your requirementsBuilt around your needs01 02 03
A clearer view of your leads and customers.
Keep enquiries together
Capture the agreed lead information and organise ownership, notes and next steps.
Work with your sales process
Define pipeline stages and follow-up rules around how your team handles opportunities.
Make the information useful
Agree dashboard views, user permissions and reporting requirements before development.
What we can createA scope that
A scope that
fits your business.
These are the kinds of work we can include.
Your proposal defines the agreed deliverables.
- 01
Lead capture and records
Define the fields your team needs, enquiry sources, contact details and a way to find or update records.
- 02
Pipeline stages and ownership
Set up agreed stages such as new enquiry, contacted and proposal sent. Assign responsibility so each lead has a clear next action.
- 03
Tasks and follow-up reminders
Scope due dates, notes and notifications around your follow-up process. Delivery channels and scheduling rules depend on the connected systems.
- 04
Customer history
Bring agreed notes, activities and documents into the record so the next person can understand the context.
- 05
Sales dashboards and reports
Define views for open leads, outstanding actions or stage totals. Each report is based on the fields and events the system actually records.
- 06
User roles and access
Agree which users may view, edit or export particular information. Administrative permissions and sensitive fields are reviewed before build.
- 07
Data import and integrations
Assess existing spreadsheets and tools, map the agreed fields and verify a sample import. API connections are included only after access and feasibility checks.
Where it fits
Start with the partPractical starting points.
your business needs.
Sales and enquiry pipelines
Record enquiry sources, assign ownership and track the next step for each lead. Define your stages rather than copying another business’s sales process.
Property and professional service teams
Scope customer records, requirement notes and follow-up views around how your team handles enquiries. Specific workflows are confirmed during discovery.
Customer and sales dashboards
Agree which information the team needs to see, which users can access it and how reports should be generated.
Who this is forChoose this service
Choose this service
when it fits the task.
Start with your business situation,
then agree the work it needs.
Property consultants
Useful when several people handle enquiries and need visibility into requirements, ownership and upcoming follow-ups.
Sales and service teams
Useful when leads move through repeatable stages and customer history needs to remain accessible to the responsible team.
Businesses outgrowing spreadsheets
Useful when an agreed process needs stronger record structure or permissions. A simpler existing tool may still be sufficient for a small workflow.
Illustrative scenariosHow this could work
How this could work
in a business like yours.
These examples explain possible uses. They are not client projects or results.
Property enquiry follow-up
A property team could capture a buyer’s location, budget and requirements, assign a consultant and schedule a follow-up. The fields and reminders would reflect that team’s process.
Service enquiry to proposal
A service company could track enquiry, discussion and proposal stages, with notes and a next-action date. A dashboard could show records needing attention without claiming that a dashboard alone creates sales.
Customisation & connectionsConfirm how the
01 02
Confirm how the
pieces will work together.
Connect lead sources
Website forms, email services and other lead sources may connect through supported APIs or provider integrations. Access, duplicate handling and field mapping are checked first.
Move data carefully
A migration needs a review of missing values, duplicated records and source permissions. Agree the records to import, how to verify them and who approves the result.
How we work togetherFrom the first
From the first
conversation to
the handover.
Each stage has a clear purpose. We agree the scope and feedback points before the project begins.
Plan your project- 01
Review the sales process
Map enquiry sources, lead stages, ownership and follow-up tasks with the people who handle them.
- 02
Define records and permissions
Agree fields, user roles, reports, integrations and the first release. Decide whether to extend an existing CRM or build a custom system.
- 03
Build the working views
Develop record screens, pipeline actions and the agreed dashboards. Review how real users complete their tasks.
- 04
Test records and connections
Check representative data, role access, reminders and imports. Verify integrations without exposing customer information in test material.
- 05
Deploy and train
Move the approved system to the agreed environment, import authorised data and explain everyday administration.
- 06
Agree continued operation
Define backups, access changes and system updates. Monitoring or feature additions require an agreed support scope.
After the delivery
A clear handover and a plan for what follows.
The proposal sets out documentation, access handover and support responsibilities. We discuss maintenance and third-party costs before you commit to the build.
Before we startPut a clear shape
Put a clear shape
around the project.
What shapes the scope
Users, workflows, data sources, integrations and permissions affect the work. Share the systems you use and the problem you want to solve.
What we confirm first
We review technical feasibility, data access and ongoing costs. Features that depend on a provider or API are confirmed before inclusion.
Tell us what you want to create or improve. We’ll review your brief and discuss a suitable scope.
Discuss Your ProjectCommon questionsA little
A little
more clarity.
Useful things to know before
scoping this service.
Do we need a custom CRM?+
Not always. We review the workflow and existing tools first. Configuration or an integration may be enough; a custom system makes sense when specific records, permissions or processes are not supported adequately.
Can it match our pipeline?+
The agreed fields, stages, roles and views can be designed around your process. Each feature is defined in the scope so later additions can be reviewed and priced separately.
Can we import our existing leads?+
We assess a sample export, field formats and duplicate records before confirming migration. You need permission to use the data, and the import is checked against an agreed mapping.
Can reminders go through WhatsApp?+
That depends on supported provider access and the messaging permissions available to your business. We do not assume WhatsApp API access or automatic messaging is included.
What affects CRM cost and timeline?+
User roles, workflows, dashboard requirements, data migration and the number of integrations affect complexity. A first release can focus on the essential lead process before more functions are added.
What happens after delivery?+
The handover can explain records, user administration and agreed reports. Hosting, backups, monitoring and future development are specified separately in the support arrangement.
Before you brief the project
All guides Useful reading.
Plan your lead workflow before building a custom CRM
Map lead sources, ownership, pipeline stages, permissions and exception handling before investing in a custom CRM or business automation.
Read the guide
Before running ads, check your landing page and lead tracking
Connect advertising messages, landing pages, enquiry forms and lead quality reporting before launching a digital marketing campaign.
Read the guideYour next step
Tell us where your leads get stuck.
Share your current tools, lead stages and the follow-ups your team handles. We will review the simplest suitable system.
Discuss Your Project