Give your firm a repeatable system for acting on client opportunities
Hearth connects CRM, client follow-up, campaigns, and workflow around the way your practice actually operates—so opportunities inside the existing client base are easier to identify, act on, and track.
Practice Management is an implementation-led capability. Hearth scopes the operating problem, connects what is required, and builds the first useful workflow around the firm's real process.
Start with the constraint, then build the system around it
Hearth does not begin with a generic CRM replacement. It begins with the part of the practice that fails to move consistently today.
When client data exists but “what happens next” is unclear.
Hearth defines stages, ownership, fields, and follow-up so tracking is usable.
When the firm sees opportunity in the client base but rarely acts on it.
Hearth helps surface relevant clients, trigger appropriate outreach, and track movement.
When outreach depends on manual reminders.
Hearth builds repeatable campaign and follow-up logic around real firm goals.
When tasks and handoffs rely on memory.
Hearth clarifies triggers, ownership, tasks, and movement between people.
Define one useful implementation before expanding the system
The first scope is concrete enough to use in production and narrow enough that the firm knows exactly what Hearth is implementing.
Define the operating constraint.
Identify the CRM, client-opportunity, follow-up, campaign, or workflow problem that matters most.
Connect only what is required.
Hearth determines which systems, data, permissions, and workflow connections the agreed scope actually needs.
Implement the first use case.
Build the defined workflow, campaign, pipeline, or operating process inside the firm's real environment.
Evaluate before expanding.
Use the implementation in practice, review the result, and decide whether additional infrastructure is warranted.
Priced per engagement, because no two practices are broken the same way
There is no published rate card for Practice Management, and a page that invented one would be lying to you. The work is custom by nature: Hearth scopes the operating problem first, then quotes the implementation that solves it.
Four things move the number more than anything else.
How many systems have to connect
One CRM configured against a single calendar is a different build than a CRM, email platform, document system, and billing tool that all have to agree on the same client record.
The condition of the data you already have
Clean records shorten the work. Duplicate contacts, partial histories, and fields that mean different things to different people take time to reconcile before anything can be automated.
How much process exists in writing
If the firm can describe how a client moves from question to engagement, Hearth builds it. If that process lives in a few people’s heads, defining it is part of the scope.
How much you want running on day one
A single workflow in production costs less than a full pipeline, campaign library, and internal task system delivered together. Most firms are better served starting narrow.
Two scopes, so the range is less abstract
Both examples are anonymized and stripped of anything identifying. They are here to show how differently two engagements can be shaped, not to imply a price.
One follow-up workflow, in production
A small firm knew a portion of its client base likely qualified for an S-Corp conversation, but the follow-up depended on whoever remembered to make the call. Hearth defined the qualifying criteria, built the list logic in the firm’s existing CRM, and wired a single outreach-and-task sequence with clear ownership at each stage.
Narrow scope, one system touched, no data migration.
Two client lists, one pipeline
A firm that had absorbed another practice’s book was running two sets of client records with different fields and no shared definition of an active engagement. Hearth reconciled the records into one structure, defined pipeline stages the whole firm could use, and rebuilt campaign and task logic on top of the merged data.
Broader scope, data reconciliation, multiple workflows.
The firm does not have to carry all of the implementation risk
Practice Management implementations include a written Hearth warranty. The coverage, eligibility requirements, and remedy for the scoped implementation are presented before the firm commits—so the firm does not have to carry all of the implementation risk alone.
Know the protection before work begins.
- Warranty period stated in writing
- Covered fees or payments identified up front
- Eligibility requirements defined before work begins
- Clear remedy if the warranty is triggered
Final approved warranty terms govern each engagement.
Review the operating implications before Hearth connects to the firm
Before implementation begins, the firm reviews required systems, permissions, data handling, client-relationship boundaries, scope, and the written Hearth warranty terms that apply to the implementation.
Systems & permissions
Review which platforms, access levels, and data connections the agreed implementation requires.
Review systems →Client relationship
Review how communication, advice, client ownership, and any Hearth-facing role are defined.
Review client protections →Security & data
Understand how Hearth handles the information required to configure and operate the agreed workflows.
Review security →Scope & warranty
Confirm the implementation scope, applicable fees, support expectations, and written warranty before commitment.
Discuss the scope →Clarify the first scope before Hearth starts building
Do we need to replace our current CRM?
Not necessarily. Hearth starts with the operating need and determines what actually needs to change, connect, or be rebuilt.
Can we start with one workflow?
Yes, where appropriate. A defined workflow, campaign, pipeline, or use case can be a practical first implementation before expanding.
What systems can Hearth work with?
Supported systems depend on the implementation scope. Hearth confirms the required integrations, permissions, and data connections during scoping.
What does the Hearth warranty cover?
The written warranty provided before implementation states the coverage period, applicable fees, eligibility requirements, and remedy for the engagement.
Start with the operating problem your firm most needs to fix
Scope one useful implementation, connect only what it requires, and evaluate the result under a written warranty before expanding the system.