Skip to content
Terramand

The platform

The platform behind the plan.

Terramand runs on a purpose-built platform for planning, running, and reporting on growth work honestly, in plain English. Here is what it does today, what gets configured during onboarding, and what is planned.

The rule we build to

No fake numbers. If a data source isn’t connected, the figure is labeled not connected — not filled in with an average. If a screen is showing sample data, it wears a sample badge.

LIVEDEMO DATAREQUIRES CONNECTION

What's in it

Four things, done properly.

01

One connected system

Your website, your CRM, your campaigns, and your reporting are configured during onboarding to share data, instead of being stitched together after the fact from vendors that were never designed to talk to each other.

02

Every number carries a status

We label every metric and integration as live, sample, or not yet connected. If a number in your report isn't your real data yet, it is marked clearly — a sample figure never quietly passes as your actual result.

03

Built around your real sales cycle

Call tracking, form tracking, and CRM pipeline stages are configured around how your business actually sells — inquiry, qualified, appointment, quote, customer — not a generic funnel that doesn't match your team.

04

Your data stays yours

You own your website, ad accounts, CRM data, and content. Our access is granted by you, scoped to the work, and revocable.

The model

The 8-stage customer lifecycle the platform is organized around.

From the moment someone learns you exist to the moment they send you the next customer. Every service, every report, and every plan is mapped to one of these stages — and the last stage feeds the first.

Stages are the planning model, not a promise of automation. What gets tracked at each stage depends on which systems are connected in your engagement.

  1. Awareness

    Someone learns you exist.

  2. Interest

    They start paying attention.

  3. Intent

    They show a buying signal.

  4. Nurture

    Relevant follow-up keeps pace.

  5. Conversion

    They become a customer.

  6. Scheduling

    The work goes on the calendar.

  7. Relationship

    The work gets done, and you stay in touch.

  8. Loyalty

    They come back, and send the next one.

  9. Loops back

    Loyalty feeds new awareness — the cycle starts again at stage one.

Functional layers

What each layer of the platform does — and where it stands.

No vendor logos. Each layer is labeled as a delivered service, something configured during your onboarding, a system you already run, or a plan.

  1. 01

    Customer Data

    Configured at onboarding

    Inquiries, calls, visits, and sales tied to one customer record in your CRM.

  2. 02

    Content Creation

    Delivered service

    The source material every channel below draws from — pages, posts, email, creative.

  3. 03

    Social Distribution

    Delivered service

    That content, published to the platforms that have a defined job in your plan.

  4. 04

    Email + Follow-up Sequences

    Configured at onboarding

    Behavior-triggered follow-up, built and tested with you during onboarding.

  5. 05

    Website Engagement

    Configured at onboarding

    Forms, calls, and on-site behavior captured as intent signals once tracking is in place.

  6. 06

    Inquiry Acknowledgment + AI Call Answering

    Per engagement / Planned

    Instant acknowledgment is configured per engagement; after-hours AI call answering is planned and offered only after it is tested with you.

  7. 07

    Scheduling / Booking

    Your system

    Won business turned into a staffed slot on your calendar, using the scheduling tool you already run.

  8. 08

    Sales + Revenue Data

    Configured at onboarding

    The sale, tied back to the campaign and channel that earned it — where you share the outcome data.

  9. 09

    Reporting

    Delivered monthly

    Spend, inquiries, new customers, and revenue in one monthly report, with every figure labeled live, sample, or not yet connected.

  10. 10

    Improvement

    Delivered service

    What the report says to fix, fed back into every layer above it on the monthly cadence.

The last layer feeds the first. What the monthly review says to fix changes what gets built, sent, and posted next — the loop is run by people, on the cadence in your plan.

Integrations

Your data stays in the systems you already run.

We connect to your stack rather than replacing it. Each connection is authorized by you, scoped to what the reporting needs, and revocable.

Statuses describe the platform today, not any one client account. A plain “planned” is less impressive than a wall of logos, but it tells you exactly what feeds your report.

  • HubSpot CRM

    Built; connected per engagement

    Contacts, deals, and lifecycle stages. Connected to your account during onboarding with access you grant.

  • Google Business Profile

    Configured at onboarding

    Posts, reviews, and listing management run in your profile with access you authorize.

  • Google Ads and Meta Ads

    Configured at onboarding

    Campaigns run in ad accounts you own. Reporting is assembled from those accounts each month.

  • Call tracking

    Planned

    Dynamic number insertion and outcome tagging — offered where it fits the plan, after it is configured and tested with you.

  • Field service and scheduling software

    Planned

    Job and revenue sync from the tools you already run. Until then, outcomes are shared with us for the monthly report.

Ownership

You own your website, ad accounts, CRM data, and content.

This is policy, not a negotiating point. The only thing keeping you with us should be that the numbers keep working.

  • Your website, your domain, your hosting account — in your name.
  • Your ad accounts, your Google Business Profile, your CRM. We are granted access; we never take ownership.
  • Your content — pages, posts, creative, and email — is yours to keep and reuse.

See it applied to your business

Request a strategy session.

We will walk you through exactly what would be connected, configured, and reported on in your engagement — and what would not.

A thirty-minute conversation with a person. No obligation.