Key takeaways
- A completed closing does not prove that the group has capacity for another acquisition.
- Schedule each scarce role in the period when its work must occur; later spare hours cannot solve an earlier shortfall.
- Keep optional group changes separate from work required for safe, lawful operations and essential payments.
- Test a shared process and its costs before relying on a saving or repeating it at another site.
Building a dental group through acquisition starts with a repeatable job
An acquisition plan should explain what the group can absorb next. A list of attractive practices answers a different question. Before approaching another seller, identify the work that a purchase will add, who can do it and what must be learned from the last purchase before repeating the process.
This guide uses integration to mean the work needed to bring an acquired practice into the buyer's chosen operating arrangements. It does not assume that every site must change its brand, software or clinical methods. The scope depends on what was bought and what the group actually plans to share.
The first 90 days guide covers acceptance of a single practice's handoffs. The group decision is whether several purchases compete for the same people, cash and systems. A site may be ready to operate while the central team still lacks room to begin another transaction.
In a December 2023 ADA guest column, BMO banker Diana Talpa discusses the extra time, systems and shared goals involved in starting a group. It is dated practitioner-facing commentary, not evidence of an ideal group size or acquisition pace. (Source: ADA: Starting a group; December 20, 2023.)
Define which work will be shared and why
Start with a specific service rather than a promise to centralize the business. For billing support, describe who prepares the claim, handles an exception, answers a patient's question and checks the receipt. For purchasing, describe who approves an order and who makes sure the correct item reaches the office.
Then name the expected benefit and the evidence needed to test it. A shared service may remove repeated work, improve its quality, or provide cover during an absence. Those are different goals. The buyer should not book a cash saving merely because a task moved to a different person.
| Proposed shared work | What must be understood at the acquired site | What the group must be able to supply |
|---|---|---|
| Billing support | Actual exception types and handoffs | Named staff, access and response capacity |
| Purchasing | Local needs and current order duties | Approved process that still serves each office |
| Payroll administration | Employer setup and local review roles | Specialist-supported setup and clear approval route |
| Financial reporting | Source periods, definitions and site identifiers | Comparable reports with local detail preserved |
| Technology support | Systems, dependencies and permitted access | A supported change plan and recovery responsibility |
| Recruiting support | The role, hours and clinical needs | A defined recruiting task, without assuming a hire |
Leave work local when the proposed center cannot yet perform it. That choice can have a cost, but it is more useful to state the cost than to assume a service exists. Record any temporary arrangement and the event that would justify changing it.
Choose the next practice by its demands on the group
Define the search criteria around capabilities as well as purchase characteristics. An office using unfamiliar systems or relying on a departing key person may need a different transition effort from one that can continue with its current team. That does not make either a bad purchase. It changes the work the buyer must support.
Keep seller facts separate from buyer plans. "The seller's manager will stay" needs evidence about that person's actual arrangement. "Our team will take over billing" needs a staffing and access plan on the buyer's side. Neither statement should stand in for the other.
Ask for a short explanation of what makes this target different from the prior purchase. Include the buyer's own learning. If the last conversion took more review time than expected, use that observation when sizing the next job. Do not carry forward an old estimate only because it made the original acquisition schedule balance.
Use the due diligence guide for the underlying transaction review. The group intake note should identify the few findings that change sequencing, staffing or shared-service design. It should not become a second copy of the entire diligence file.
The second-practice guide tests incremental contribution after effects on the first office. Carry that supported case into the group plan. A sound economic addition can still compete with another purchase for the same implementation team.
Separate operating readiness from optional group changes
Some work is needed for safe, lawful operations or essential payments. Other work supports a chosen group standard. Name the difference before setting a common change date. A required correction should not wait for another practice to finish its elective software or branding project.
CDC's dental guidance addresses training for staff at orientation and when tasks change, alongside policies suited to the dental setting. Have the responsible clinical team include the affected work in its plan. A business integration calendar does not establish clinical readiness. (Source: CDC: Dental administration; May 15, 2024 guidance.)
For each planned change, identify its prerequisites. A central reporting process may need a stable location identifier before a combined report becomes useful. A shared call route may need working local escalation before staff can handle a complex inquiry. The prerequisite should be an observable result, not merely a meeting that has occurred.
| Decision point | Group question | Evidence that keeps the decision open |
|---|---|---|
| Before committing to another purchase | Can the team support the overlapping work? | Unassigned hours or an unresolved funding source |
| Before moving a process to the center | Can the receiving team perform the actual work? | Training completed but important exceptions unresolved |
| Before a shared system change | Has the affected scope been tested and reviewed? | Missing site, account or imaging-link evidence |
| Before claiming a saving | Did the old cost end and what replaced it? | Local work continues without funded support |
| Before repeating the same change elsewhere | What did the first implementation prove? | Rework still open or no result measured |
The table sets planning questions, not legal conditions for every sale. Have the appropriate advisers determine the actual closing and operating requirements. Keep contractual deadlines visible, including what happens when a planned change cannot be completed before them.
Count the scarce person's hours before overlapping purchases
Use the person or team that constrains the schedule. Total staff hours can be misleading when only one person can validate a report or approve a change. Separate roles that cannot substitute for each other. The following invented example isolates one integration lead; it is not a complete staffing plan.
Assume the lead has 100 hours per month available after existing duties. Practice A needs 80 lead hours in its first month and 40 in its second. Practice B needs 60 in its first month and 20 in its second. All work is assigned to the displayed month and must be completed then under the supplied plan.
| Planning month | A and B begin together | B begins one month after A | Available lead hours |
|---|---|---|---|
| Month 1 | 140 | 80 | 100 |
| Month 2 | 60 | 100 | 100 |
| Month 3 | 0 | 20 | 100 |
| Total planned work | 200 | 200 | Not a substitute for monthly limits |
Starting together creates a 40-hour shortfall in month one. The spare time in month two cannot perform work that was required earlier. Staggering the starts produces demands of 80, 100 and 20 hours. It fits the stated monthly limit, but leaves no unused lead time in month two.
Both options require the same 200 hours. The staggered plan changes timing; it does not create a saving. It also assumes the transaction dates and interim arrangements can be changed. The buyer must confirm that with the parties rather than using a spreadsheet to rewrite a signed obligation.
Check the other scarce roles before selecting a plan. A schedule that fits the integration lead may fail for the clinical reviewer or outside software team. Map these constraints separately. Their hours cannot simply be pooled into one number if their work requires different skills or authority.
Test rework and staff absence as separate constraints
First change only Practice A's second-month demand from 40 to 55 hours. In the staggered plan, month two now needs 55 plus 60, or 115 lead hours. The shortfall is 15 hours. That is an invented rework scenario, not an estimated likelihood of a difficult integration.
Suppose qualified outside help can perform exactly those 15 hours of work at an assumed all-in cost of $90 per hour. The added cash cost is $1,350. This resolves the modeled capacity gap only if the work can be delegated and the help is available. Hours reserved for the buyer's own decisions may remain a constraint.
In a separate sensitivity, return to the original work estimates but reduce the lead's month-two availability to 80 hours. The staggered demand remains 100 hours, leaving a 20-hour gap. Adding the 15-hour helper from the other case would still leave five hours unresolved, if that help were usable for this different work.
| Independent change to the staggered base | Month-two demand | Month-two capacity | Gap before a response |
|---|---|---|---|
| Original assumptions | 100 hours | 100 hours | 0 hours |
| A requires 15 extra hours | 115 hours | 100 hours | 15 hours |
| Lead availability falls by 20 hours | 100 hours | 80 hours | 20 hours |
The cases do not assume rework and absence happen together. A combined scenario would need a new calculation and an explicit response. Do not assign a probability or confidence score to these cases without evidence. Their purpose is to expose the task, period and decision that would change the acquisition plan.
Treat a database merge as its own project
Buying a practice, changing its software and combining its database are different decisions. A common owner does not make every system change urgent. Ask what the group needs to accomplish and whether a less disruptive reporting arrangement can serve that need while the team reviews the full merge.
Open Dental's merge documentation calls for a test merge and review before the final merge. It explains that patient numbers can change in merged databases, which can affect imaging links. It also warns that a merged live database cannot be reverted to the original databases after use. These are product-specific facts. (Source: Open Dental: Database merges; reviewed September 10, 2026.)
Build the work estimate from the actual systems and approved scope. Include review by the people who understand the local records and workflows. A successful transfer of files does not by itself prove that the right person, account or image is linked in the new environment.
For HIPAA-regulated organizations, HHS risk-analysis guidance includes electronic patient information across connected locations. (Source: HHS: Risk analysis; reviewed September 10, 2026.)
Have the privacy and technical team determine the permitted access, transfer method and review needed for the planned change. An NDA for commercial diligence does not grant unrestricted patient-data access. Keep these decisions outside a buyer's informal task list and tied to the responsible professionals.
Keep the economics tied to completed changes
Maintain separate columns for the current cost, the approved change, its one-time cost and the result after implementation. A proposed billing center may need extra local help during conversion. Include both costs for the period when both teams are working; remove the old cost only when the underlying work and obligation end.
Ask who owns each claimed benefit. For a faster report, specify the reporting period, delivery date and defects that matter. For a reduced expense, identify the old invoice or payroll cost and its replacement. A group margin can improve for reasons unrelated to the change, so use evidence that tests the specific claim.
Protect the original acquisition case. Keep it beside the revised operating plan rather than replacing it with new estimates. That record helps the buyer see whether an error came from target selection, cost assumptions, timing or execution. Each cause implies a different adjustment before the next purchase.
Keep the cash cost of overlapping work in the working-capital plan. The loan underwriting guide addresses the funding discussion. An operating plan that fits available hours can still fail if the required help cannot be paid on time.
Decide what must be proved before the next commitment
Create a short decision record before approving another acquisition. State which shared services now work, what remains dependent on the seller or temporary help, and how much capacity is already committed. Keep the conditions tied to the next target's needs. A perfect score on unrelated tasks should not outweigh one critical missing capability.
Use a pause as a specific operating choice. Name what must be resolved, the evidence expected and the person who can decide when the search or commitment resumes. Avoid an indefinite "stabilize first" instruction that gives the team no way to show progress.
The buyer may continue researching future targets while declining to commit to overlapping implementation work. Keep those states distinct. A conversation, a signed agreement and a funded purchase create different demands and obligations. Review the consequences of each commitment with the transaction team.
Tell affected staff what their work requires them to know, with clear authority and timing. Someone assessing a proposed shared process may need involvement before the wider announcement. Coordinate that role with the seller and respect required notices, patient privacy and clinical duties. Staff participation should solve real work rather than serve as a fixed secrecy rule.
Common mistakes when adding acquired practices
One error is treating every completed closing as proof that the group can absorb another office. Closing tests one set of conditions. A repeatable operating capability needs its own evidence. Look at unresolved work and actual team demand before reusing the schedule.
Another mistake is assuming the most knowledgeable employee has unlimited spare capacity. Asking that person to keep the existing office running while solving every new site's problems can create a hidden bottleneck. Name the tasks and fund the support, or revise the scope and dates where the agreements permit.
Do not force every office onto a common system simply because it makes the organization chart look cleaner. Define the purpose, required review, change cost and limits on reversal. Equally, do not leave a harmful process untouched for the sake of a smooth transition. Qualified professionals must resolve urgent care, legal and security concerns promptly.
Summary: let proven capacity set the pace
Build the acquisition sequence around the work each purchase creates and the people who can perform it. Test overlapping demands in the periods when the work must occur. Count savings after the required changes are supported, and use each completed project to improve the next estimate. Keep the next commitment tied to capabilities the group can demonstrate.
Bring the next acquisition into the operating plan
Use the buyer guide to connect the search, transaction and operating plans. To discuss a proposed acquisition sequence, schedule an intro call with Jason Taken at HedgeStone.
Frequently asked questions
How fast should I acquire practices when building a group?
Use the work created by actual targets and the team's supported capacity. Identify overlapping duties, cash needs and required decisions. There is no standard acquisition interval in this guide. A change in transaction dates also needs agreement from the relevant parties.
Is integration complete as soon as the practice closes?
Closing and integration answer different questions. The purchase can complete while shared-service work remains open. Confirm what the site needs to operate and what the central team still must do before using that team for another acquisition.
Does staggering purchases reduce the total work?
Not in the supplied example. Both plans require 200 integration-lead hours. Staggering changes when those hours are needed and avoids the original first-month shortfall. It leaves no spare lead time in the second month, which still deserves a separate stress test.
What if the acquired practice needs more work than planned?
Name the additional task, skill and period. In the example, 15 extra hours create a second-month gap. Qualified help at the supplied $90 hourly cost would add $1,350, but only if the work can be delegated and the person is available.
Must every acquired office move to the same software immediately?
No universal migration schedule is proposed. Define the business purpose, permitted scope, review work and system dependencies before choosing a change. A common reporting need may have an interim solution while the group assesses a larger conversion or merge.
Can I undo an Open Dental database merge after using it?
Open Dental's reviewed documentation says that a merged live database cannot be reverted to the original databases after use. Treat that as a product-specific limitation. Review the test merge, affected links and required follow-up with the vendor and authorized team before proceeding.
When can I include a central-service saving in the plan?
Keep the current cost, proposed change, one-time spending and actual result separate. Establish what work ends locally and what replaces it. Retain costs for periods when both teams still perform necessary work. A changed cost allocation alone does not prove a saving.
What evidence should come before the next acquisition commitment?
Show which shared services work, what remains dependent on temporary help, the hours already committed and the next target's different needs. Give each open condition an owner and required evidence. Review contractual consequences before changing a planned commitment or date.
Sources
Retrieval dates appear beside each source. Figures retain their stated observation years; retrieval does not make older data current.
- ADA: Starting a group · Retrieved
- CDC: Dental administration · Retrieved
- Open Dental: Database merges · Retrieved
- HHS: Risk analysis · Retrieved