Growth Engine is an added-responsibility decision. It is not a claim that one plan produces better business results than another.
The plan includes the responsibility already carried by Local Authority, then adds a clear page for each core service named in the agreement, email and text content for the business’s existing customer list, and a monthly strategy call. The website, Google profile, search work, reviews, and customer content are reviewed as connected work.
Marque & Heir’s public Growth Engine page, checked August 25, 2026, is the source for the plan inclusions described here. The signed agreement controls the exact work. Marque & Heir recommends the larger scope only when the business needs those added responsibilities handled. The owner still supplies the real facts, customer-list permissions, access, and approvals the work requires.
Start with the services the owner has approved
Growth Engine adds dedicated core-service pages. It does not give the website shop permission to decide what the business offers.
The owner should name the core services that belong in the agreement and approve the facts behind each one. That includes the service name, what the business handles, what it does not handle when the boundary matters, where it is available, and the next step a customer can actually take.
For any business, the coverage statement must still come from the owner’s approved record. A wide market is not permission to add locations or describe work the business has not approved.
Exact page counts belong in the signed agreement. “A page for each core service” means each core service named in that agreement, not every possible variation someone thinks of after the work begins.
Give each page one clear job
A dedicated page should help a customer understand one approved part of the business without sorting through a general paragraph.
Marque & Heir recommends that the working brief for each page name:
- The approved service and plain explanation
- The real owner-supplied facts and photography
- The scope or exclusion that prevents a wrong assumption
- The questions the business can answer responsibly
- The approved contact path
- The person who approves the final page
- The live check that marks the page complete
That list is a working recommendation, not a public promise about an exact page format. The signed agreement and owner approvals control the actual work.
A completed service page proves that the agreed page was approved, published, and checked. It does not prove rankings, calls, inquiries, revenue, or sales.
Customer email starts with the existing list
Growth Engine adds email content for the business’s existing customer list. The list comes from the business. It should not be invented, purchased, or filled with sample contacts to make the setup look ready.
The owner supplies the approved list, the real business update or question the content will address, the reply destination, and the person who approves the final words. Exact message counts, timing, building, sending, and reporting responsibilities belong in the agreement.
“Email content” should not be stretched into every email task. The scope should say what is prepared, which approved source material is used, whether a send is included, who performs the final send check, and who handles replies.
No email should promise an offer, date, availability, or business action the owner has not approved.
Text content stays behind its gates
Growth Engine also adds text content for the existing customer list. That work does not switch on just because the draft is ready.
The current public Growth Engine page states that text begins only after messaging registration clears. Marque & Heir recommends keeping that condition, the approved permission record, and qualified review visible in the agreement, monthly record, and owner review.
The business supplies the approved list and permissions. The approved message purpose, wording, reply route, and stop handling must be settled before use. If messaging registration or a required permission is pending, label the text work pending. Do not describe it as live.
A prepared message is a draft. An approved message is ready for the next named step. Neither status proves delivery, a reply, a booking, or a sale.
Connected work still needs separate records
Growth Engine treats the website, Google profile, search work, reviews, and customer content as connected responsibilities. Connected does not mean every surface becomes one undivided task.
Each item should still have an approved source, owner, status, destination, checked date, and next action. A website page can be live while an email remains in review. A profile update can be approved while text content waits on its gate. The monthly record should preserve those differences instead of covering them with one general status.
Marque & Heir uses the monthly record to let the owner review related work together while keeping each surface’s completed work and holds separate.
The monthly call has a defined job
The current public Growth Engine page says the plan includes a monthly call to decide what happens next. Marque & Heir recommends using that call to review what happened, what comes next, and why.
The call should begin from the current working record. Completed work, live checks, open holds, owner decisions, and next agreed actions should be visible before the conversation starts.
The call is not a license to invent a forecast or turn every idea into new scope. A new request should be recorded, compared with the agreement, and approved before it becomes assigned work.
The monthly report is the current record
The current public Growth Engine page states that the monthly report is part of the plan and that dashboard access is added as it comes online.
Keep those two facts separate. Do not describe the dashboard as included and live before it is actually available under the signed scope. Do not replace the current report with a promised future screen.
The report should state the work covered, the source and date behind any number, the status of each meaningful item, and the limits of what the record proves. Missing information stays unknown. A staged item stays staged until the live check passes.
Owner approval remains part of the work
The added responsibilities do not remove the owner from business decisions.
The owner supplies current facts, access, approved photography, the existing customer list, required permissions, the offer, and timely public approvals. Marque & Heir prepares and handles only the pages, content, connected work, reporting, and owner review named in the agreement.
Marque & Heir recommends making that boundary readable before work starts. The written record should state what can move, what is waiting, and which decision belongs to the business.
Exact counts and edges stay in the agreement
The public plan describes the responsibility. The signed agreement gives it exact edges.
Before Growth Engine begins, the agreement should name the core-service pages, content counts, intended channels, approval path, outside gates, monthly-call responsibility, reporting record, owner inputs, exclusions, and handoff. If a new page, message, list, or connection is requested later, record it as a change instead of assuming it is included.
Marque & Heir uses those written edges to state the finish line without treating the plan as the answer for every business.
The public price does not decide the fit
The Marque & Heir Pricing page and Growth Engine page, checked August 25, 2026, list Growth Engine at $5,500 to build plus $4,500 per month, with a three-month initial term, then month-to-month.
Those are the dated public price and term. They do not forecast an outcome. Marque & Heir recommends Growth Engine when dedicated core-service pages, existing-customer email and gated text content, connected public work, and a monthly owner review need one written home. A narrower or broader responsibility may call for a different answer.
Bring the added responsibility to the free check, keep the findings, and choose Growth Engine only when the pages, customer content, and monthly owner review belong in the written job.