Pricing and investment, explained. Understand what shapes the engagement before a proposal. Every TQP engagement is written as separate, labelled lines: what is paid once, what continues, what moves with use, and what comes from someone else.
Based in TorontoServing the United States and Canada
Statement · Conversion Website with Platform Foundation
Illustrative
| Key | Line | Type | Amount |
|---|---|---|---|
| 1 | Conversion WebsiteStrategy, design, build, intake path and launch | One-time | Starts at $4,995 |
| 2 | Platform FoundationRecords, inbox, booking, reminders and reviews | Recurring | From $197/mo |
| 3 | Calls, texts and emailReported each month | Billed by use | By use |
| 4 | Phone number and carrier registrationSet by the carriers | Separate provider | Separate |
Every published starting price in one place, smallest step first. Most owners begin with one piece and add the next when the business needs it.
| Offer | What it does | Starting price | Link |
|---|---|---|---|
| Essential Website | A professional website of up to 10 pages, designed, written, hosted and kept current for you. | $99/month, no setup fee | See the Essential Website |
| Get Found local SEO | Your Google Business Profile, listings and local search foundation, managed. | $99/month, or $82.50/month billed yearly | See Get Found |
| Smart Website | A custom website with booking, customer records and follow-up behind it. | From $2,395 setup + $197/month | See Smart Websites |
| AI receptionist | Answers calls, captures the details and books or routes the caller. Usage billed at actual use. | From $1,495 setup + $497/month | See the AI receptionist |
| Review growth | Asks every finished customer for feedback and a review, and flags problems for recovery. | From $995 setup + $297/month | See review growth |
| Signature Systems | The whole system designed, installed and run by our team, AI included. | From $995/month | See Signature Systems |
Accounting firms have their own client intake and booking system: $197/month for one user, up to $497/month for 7 to 10 users. Setup, monthly and usage charges always stay on separate lines.
Most confusion about what a system costs comes from lines being blended together. A monthly fee that secretly includes usage, a setup price that quietly assumes nothing will change, a support plan nobody can describe. We keep six kinds of line apart, mark each one the same way everywhere on this page, and name them in your proposal.
| Line | What it pays for | When | What changes it | For example |
|---|---|---|---|---|
| One-timeImplementation | Strategy, design, writing, building, configuration, connections, testing and launch of the scope in your proposal. | Agreed before work begins and billed as the proposal sets out. | Only if the scope changes, and only after you approve the change. | A Smart Website System, the setup of an AI Receptionist, or the build of a Custom Business System. |
| RecurringSoftware and care | The connected software your team uses every day, and website hosting and care where TQP hosts the site. | Monthly, from the point the proposal names. | When you choose a different plan or add software the proposal did not include. | Platform Foundation for a TQP website, or the broader AI Business OS. |
| RecurringOperated responsibility | What TQP keeps doing after launch for an installed product: monitoring, repair, reviewing exceptions and improving the agreed path within scope. | Monthly, sometimes with an initial commitment period that the proposal states. | When the responsibility changes, such as more call paths, locations or processes. | An AI Receptionist or an Automation System that TQP operates. |
| Billed by useUsage | What the system actually consumes: calls, SMS and MMS, email, and AI model or agent consumption where it applies. | Billed separately based on use, with reporting you can see. | Month to month, with your volume. It rises when you are busy. | The minutes of calls an AI Receptionist answers, or the texts your reminders send. |
| Separate providerSeparate providers and your own tools | Phone numbers, carrier and messaging registration, payment processing, advertising, print and postage, and software you already own and keep. | Paid to the provider directly or shown as its own separate line, as the proposal states. | When those providers change their prices, which neither of us controls. | Carrier registration so business texts deliver reliably, or your existing accounting software subscription. |
| Only if you askAdditional work | Anything new after launch: a campaign, a page, a workflow, a new location or a strategy project. | Described and priced before it begins. Never added quietly. | It is a new decision every time. | Adding a second service line to intake, or a reactivation campaign next season. |
There are two ways a TQP engagement is priced, and knowing which one you are looking at explains most of what follows.
A standard product has a defined job and a published starting price. A Smart Website System, Platform Foundation or an AI Receptionist each has a clear scope, a standard launch process and a price that begins from a known floor.
Your proposal still confirms the details, but the shape of the work is already known, which is why the price can be published.
A connected system begins with diagnosis, then a written recommendation and proposal. When several journeys, locations, integrations or real exceptions are involved, the work cannot be priced honestly until those inputs are known.
Neither path asks you to assemble a package from a menu. The Systems Review decides which one you need.
Smart, Conversion and Authority are three depths of the same practice. The difference is not page count. It is how much a buyer has to decide before contacting you, and how much the website has to explain, prove and route to support that decision. Prices below are published starting floors for implementation; software is a separate recurring line.
| Smart Website System | Conversion Website | Authority Website | |
|---|---|---|---|
| Choose it when | You need to be understood quickly and contacted easily. | Several kinds of buyer have to find the right service and take the right next step. | Expertise, reputation and search visibility decide which firm a serious buyer trusts. |
| The buyer is deciding | Is this the right kind of business for me? | Which service do I need, and am I a good fit? | Is this the firm I trust with something important? |
| What the depth adds | Focused positioning, a technical search foundation, essential buyer answers and one clear intake path, launched through a standard process. | Original positioning and conversion copy, custom design, deeper search and AI-ready answers, clear service paths, guided intake and a stronger software connection. | Deeper market positioning, brand and proof systems, broader expertise architecture, a flagship SEO, AEO and GEO foundation, plus one buyer guide or decision resource. |
| Software | Connects to Platform Foundation or the AI Business OS. | Connects to Platform Foundation or the AI Business OS. | Runs with the AI Business OS. |
| Probably not for | Firms whose buyers compare several services or need extensive proof before they get in touch. | A single-service business with one simple path from visit to booking. | Businesses whose buyers decide mostly on availability and speed rather than expertise. |
| Starting floor | Starts at $2,395 | Starts at $4,995 | Starts at $7,975 |
The full comparison, with examples of each depth, lives with Website Systems.
Implementation follows explicit complexity, risk, and delivery inputs. Industry may change those inputs; it never acts as a hidden multiplier. Each driver below runs from what tends to stay simple to what adds real work, so you can see where your own business sits before a proposal is written.
| Driver | Tends to stay simple | Moderate | Adds real work |
|---|---|---|---|
| Customer journeysHow many distinct buyer and customer paths must work, and where each one begins and ends. | One path, start to finish. | Two or three paths with different rules. | Many paths across services, teams or locations. |
| Locations, teams, and routingThe calendars, roles, permissions, departments, locations, exceptions and escalation paths involved. | One team and one calendar. | Several roles or calendars. | Multiple locations with their own routing and permissions. |
| Integrations and migrationThe systems, records, content, data movement, vendor coordination and cleanup required for launch. | Everything works inside one platform. | One existing tool connected, basic contacts moved. | Several systems connected and history moved from a retiring one. |
| Content and authorityThe positioning, proof, service information, decision support and machine-readable facts the experience needs. | Content exists and needs organising. | Content needs rewriting for new service paths. | Research, new proof and a body of expert answers. |
| Privacy and operating riskThe controls, testing, fallback, human review and reliability the context requires. | Low sensitivity; a mistake is cheap to fix. | Personal details that need careful handling. | Sensitive or regulated situations with human review built in. |
| Launch constraint and criticalityThe deadline, dependencies, continuity requirements and the consequence of a failed handoff. | Flexible timing, nothing depends on the date. | A season or campaign sets a target. | A fixed deadline with continuity that cannot slip. |
| Number of servicesHow many distinct services need their own explanation, questions and next step. | One core service. | A handful with different buyers. | Many services with different rules and people. |
| Proof and evidenceWhat must be gathered, verified and presented so claims are honest and persuasive. | Reviews and credentials already exist. | Case notes and examples need writing up. | Structured evidence across several services. |
| Workflow complexityHow many rules, branches, timers and exceptions the system follows after the first contact. | A confirmation and a reminder. | Follow-up with stop rules and an owner. | Branching follow-up, qualification and handoffs across teams. |
Recurring investment reflects the responsibility TQP accepts after launch, not unlimited access to labor or every capability in a platform. Software access is one part of it. The larger part is what someone keeps watching, repairing and improving on your behalf.
The proposal names what is included, what is billed by use, and which subscriptions stay client-owned. Consumption never hides inside an unrelated TQP responsibility line.
This is a deliberate choice. A single all-in number looks simpler, but it either overcharges your quiet months or hides costs in your busy ones. Separate, reported lines let you see exactly what drove a change, and they keep the recurring price tied to responsibility rather than to how many texts went out.
Phone numbers, calling, carrier, and registration
Numbers and minutes come from telephony providers. Carriers require business text messaging to be registered before messages deliver reliably, and they set those fees.
Messaging, email, and conversation consumption
SMS, MMS and email are billed by volume, so a reminder-heavy month costs more than a quiet one.
AI model or agent consumption where applicable
Installed AI products consume model time as they work. That consumption is reported and billed by use.
Payment processing
If customers pay through the system, the payment processor's own fees apply.
Advertising, media, print, and postage
Media spend and printing belong to those providers. TQP does not buy advertising.
Client-owned software or subscriptions retained by the client
Tools you already pay for and keep stay on your own account.
Third-party services approved for a specific integration
If a connection needs another service, it is named and approved before it is used.
Buyers are often told a price depends on who they are. These things do not move a TQP proposal on their own.
Industry is context. It can change real inputs such as routing or risk, but it is never a hidden multiplier on the price.
A large firm with one simple path can need less work than a small firm with complicated routing and several services.
AI is priced by the job it does and the responsibility it carries, not by the label on the request.
Connecting to a tool that does its job is usually less work than replacing it, so keeping it rarely adds cost.
The written proposal names implementation, recurring responsibility and usage treatment before any work begins, so you can compare and ask.
Responsibility is part of the price. Every line on the statement belongs to someone, and the proposal says who, so there is never a debate later about whether something was covered.
A first proposal is not a permanent ceiling. Businesses grow, add services and change how they work. This is how each kind of change is handled.
A Smart Website System can grow into a Conversion Website when the business adds services or buyer paths. The added work is scoped on its own.
Teams that outgrow Platform Foundation can move to the AI Business OS for broader software and standard automations.
An AI Receptionist, Conversational AI System or Automation System can be added later with its own setup and recurring lines.
New work after launch is described and priced before it begins, and never bundled in automatically.
Usage lines change month to month. Reporting shows what drove them.
Some installed products carry an initial commitment period. The proposal states it in plain terms before you agree.
A new location, calendar or department adds routing, permissions and testing. It is scoped as an addition, and the existing locations keep running while it is prepared.
Everything on this page is explanation. The proposal is the document that actually decides. It is written before work begins, and nothing changes it without your approval.
Choose a kind of business to see how its statement is usually built. These are common patterns drawn with published starting prices, not client records or a menu. A Systems Review confirms what actually fits.
An independent bookkeeper whose referrals check the website before calling, and who wants booking without phone tag.
Illustrative statementUsage and provider lines carry no fixed amount
Every amount is a published starting point. A Systems Review confirms the lines, and the proposal confirms the amounts.
A multi-partner firm where prospects compare expertise, services differ, and partner time is expensive.
Illustrative statementUsage and provider lines carry no fixed amount
Every amount is a published starting point. A Systems Review confirms the lines, and the proposal confirms the amounts.
A busy trade business losing jobs to calls that ring out during site visits and after closing.
Illustrative statementUsage and provider lines carry no fixed amount
Every amount is a published starting point. A Systems Review confirms the lines, and the proposal confirms the amounts.
A clinic group with several locations, calendars and staff roles sharing one customer record.
Illustrative statementUsage and provider lines carry no fixed amount
Every amount is a published starting point. A Systems Review confirms the lines, and the proposal confirms the amounts.
A firm whose qualification, routing and follow-up genuinely run on rules no standard setup was built for.
Illustrative statementUsage and provider lines carry no fixed amount
Every amount is a published starting point. A Systems Review confirms the lines, and the proposal confirms the amounts.
Buyers are often wary of the moment price comes up, because it tends to arrive late, verbally and bundled. Ours arrives in writing, line by line, after we understand the journey, and nothing starts until you approve it.
We talk through what you sell, the tools and handoffs you have, the journey that is breaking, volume and exceptions, what has been tried and who decides. No prices are guessed in this conversation.
You receive the starting path we suggest, the reasoning, and what we suggest you do not buy yet. Sometimes the recommendation is a smaller fix or no project.
Every line is named: implementation, recurring software and responsibility, usage treatment, separate provider costs, assumptions, exclusions, ownership, validity and the change boundary.
You compare it, ask about any line and choose whether to reduce scope. Removing a driver, such as a second location or a migration, visibly changes the number.
Nothing starts until the proposal is approved. From then on, any material change follows the same written path.
Most overspending on business software is not a bad price. It is money spent on the wrong line: paying monthly for something nobody set up, or paying to build something the business did not need. These are the patterns we see most often, and the reason a proposal names the handoff each line is meant to fix.
Capable tools that nobody configured end up as another login. The subscription runs every month while the missed calls and messy booking continue exactly as before.
Many businesses already own reminders, review requests or a shared inbox inside software they pay for. The cheapest improvement is often turning on what is already there.
A monthly fee that promises to handle everything rarely says what everything means. When the work is undefined, the most important task is usually the one that slips.
Designing software around the unusual case costs more to build and to change. A standard configuration for the common case, with a person handling the rare one, is usually cheaper and calmer.
If visitors already get in touch, a new site moves money to the wrong end of the journey. The break is often after the enquiry arrives, not before.
A new product that does not close a specific handoff tends to add one. Every purchase should name the step it removes, the wait it shortens or the repetition it ends.
Prices only compare fairly when the lines underneath them match. Before choosing between proposals, ask every provider the same eight questions and write the answers side by side. A proposal that cannot answer them clearly is usually cheaper on paper than it is in practice.
We would rather you asked. The proposal after a Systems Review answers each of these in writing before any work begins.
The same outcome can be reached three ways. The price differs by who carries the setup risk and who supports the result afterward, not by markup.
Fits whenYou have the time to configure it, the judgment to make setup decisions, and no pressing deadline.
The tradeoffYou own every configuration choice, every connection and every fix when something is set up wrong.
Fits whenYou want a proven setup installed correctly the first time, with a clear support boundary after launch.
The tradeoffThe configuration follows a standard path. Business-specific exceptions are scoped separately.
Fits whenThe process has rules, exceptions or integrations a standard configuration was not built to hold.
The tradeoffIt costs more to build and support because more of it is designed around your business.
These dedicated routes explain standard products in their own context. They are not a cross-offer comparison or a ceiling for a connected system.
Every term used in a TQP proposal, defined once, so the words mean the same thing on this page, in the review and in the document you sign.
Yes. The approved proposal states implementation, recurring responsibility, separate usage treatment, assumptions, validity, and the agreed scope before work begins.
The difference comes from explicit journeys, locations, routing, integrations, migration, risk, criticality, support, and operating responsibility. Industry is context, not a hidden multiplier.
The written proposal defines the original boundary. A material change is reviewed, documented, and approved before it changes delivery responsibility or commercial terms.
No. Website prices are starting floors for one-time implementation. Software, any operated responsibility and usage are separate lines, and the proposal shows each one.
Because they move with your volume. Bundling them would mean either overcharging quiet months or hiding costs in busy ones. Separate, reported usage keeps both honest.
Yes. Most engagements start with the one change doing the most damage now. Later additions are scoped and priced on their own before they begin.
Often, yes. If a tool already does its job without daily friction, the proposal usually connects to it. Replacement is scoped when the tool itself is the constraint.
Whatever the proposal names: the monitoring, support window and change process for the products and customer journey you approved. Nothing continues informally beyond that.
Anything new after launch, such as a campaign, a page, a workflow or a new location. It is described and priced before it starts.
The proposal assigns ownership of accounts, assets, data, access and documentation explicitly. Your business facts, approvals and customer relationships stay with you.
Because a buyer deserves to know the order of magnitude before booking a conversation. Starting floors describe the simplest proper version of each standard product; the proposal explains any movement from there.
Its cost depends on explicit journeys, integrations, risk and continuing responsibility that cannot be known until the process is reviewed. Publishing a single number would either mislead simple buyers or understate complex ones.
Usage lines fall with your volume because they are billed by use. Recurring lines reflect the software and responsibility you chose, so they stay until you change the plan or the scope.
Sometimes. Supplying finished content, gathering proof, making decisions quickly or keeping a simpler scope all reduce real work, and the proposal shows the effect. What stays with TQP is anything we are responsible for testing and supporting afterward.
Usage is billed separately based on use, with reporting that shows what was consumed, such as call minutes, messages and AI consumption, so a change in the bill can be traced to a change in activity.
Software alone gives your team access. An operated product adds responsibility: someone monitors the agreed path, repairs failures, reviews exceptions and improves it within scope. You are paying for that ongoing attention, not only for a login.
Usage such as calls, texts and email, carrier and phone number fees, payment processing if you take payments, any advertising, and the software you already own and keep. The proposal lists the ones that apply.
We will confirm what can stay, what must change, who owns each responsibility, and what the proposal needs to include.