Process and requirement map
Lead sources, qualification rules, stages, ownership, required fields, permissions, reporting, and exceptions.
Harmita services
CRM setup.
A process your team can follow.
We begin with the way enquiries are received, qualified, owned, and progressed. The CRM configuration follows that process, with clear data rules and only the automation the team can support.
Scoped to your project
A defined outcome.
Reviewable work.
- Pipeline based on a real process
- Data and ownership rules documented
- Team handover built into the scope
Final deliverables, schedule, fees, and responsibilities are confirmed in a proposal.
Where it fits
Useful when the problem is clear.
These are common starting points, not a qualification checklist. Discovery confirms whether this service is a sensible fit.
- A team moving from spreadsheets to a shared lead process
- A business with an existing CRM that staff use inconsistently
- A sales team that needs clearer stages, ownership, and follow-up
- An organisation preparing a defined migration between systems
Problems to solve
Start with the friction, not a package.
A useful brief names what is failing today and what a better operating state would look like.
- Leads have no consistent owner or next action
- Stages mean different things to different people
- Records are duplicated, incomplete, or difficult to report on
- Automations fire without a clear operating rule or exception path
Possible deliverables
Concrete work you can review.
The proposal selects and adapts the deliverables needed for your objective. Items not named in the proposal are not implied.
Core CRM configuration
Agreed objects, fields, stages, views, access levels, and naming conventions in the selected account.
Data migration plan
Source inventory, cleanup responsibilities, field mapping, sample import, validation, and reconciliation.
Approved automations
Defined assignment, reminder, notification, or follow-up rules with owners and documented conditions.
Reporting and team handover
Operational views, basic reporting, role-based walkthroughs, and concise process notes.
How the work moves
Decisions and inputs are visible.
Each stage names what Harmita does and what we need from your team, so dependencies do not disappear inside a timeline.
- 01
Observe the current process
Map how a lead arrives, who owns it, what qualifies it, and where information is lost.
Needed from you: Process owners, sample records, current reports, roles, and required decisions.
- 02
Approve the operating model
Agree on stages, definitions, fields, permissions, data standards, and exceptions.
Needed from you: Decision-makers for process, data, access, and required compliance review.
- 03
Configure and rehearse
Build the approved setup and test it with sample journeys and representative users.
Needed from you: Platform access, representative users, realistic records, and consolidated feedback.
- 04
Migrate, train, and stabilise
Complete approved data steps, train users, and record open items and ownership.
Needed from you: Final data approval, team attendance, a launch owner, and support decisions.
Quote factors
What shapes scope and fees.
Fees are quoted after the scope is understood. The factors below usually change the effort, dependencies, and delivery plan.
- Team size, roles, and permission model
- Number of pipelines, objects, and integrations
- Volume, quality, and history of source data
- Automation and reporting complexity
- Training, documentation, and support needs
Boundaries and dependencies
Clear before work begins.
- CRM licences, add-ons, message charges, and vendor fees are separate unless explicitly included.
- Migration quality depends on source data; cleanup ownership is agreed before import.
- Automation supports a defined process but does not replace operational ownership, staff training, or sales judgement.
Questions, answered
A few things you might ask.
Questions about crm setup, project scope, dependencies, and working with Harmita.
Which CRM should we choose?
It depends on process, roles, budget, integrations, reporting, and internal ownership. A selection exercise can compare a short list against those needs.
Can spreadsheet data be imported?
Usually, after review for duplicates, missing values, inconsistent formats, field mapping, and history needs. A sample import should be validated first.
Can you improve our existing setup?
Yes. We can review adoption, fields, stages, permissions, automation, data quality, and reporting, then scope priority changes.
Is training included?
Role-based handover can be included. The sessions, participants, materials, and follow-up support are agreed in the scope.
Useful next reading
Connect this work to the wider system.
Continue with a related service, practical guide, or browser-based tool.
A sensible next step