OUTBOUND DRAFTING THAT DOES NOT SEND

    Drafts from the record. You send.

    We draft the approach from what this utility has argued about, who is on the map, and what you offer. You send, from your own inbox. Shorten the path from prospect to contract.

    You send. Three drafts, pitched at what this utility has argued about and who you met. The only Send button is in your stack, on your domain.

    Context in, three drafts out, you sendIllustrative utility

    A stakeholder map is still only knowledge. The reason to build one is that it makes the writing possible.

    A first approach to someone who has never heard of you is a different letter from a follow-up to a person you met at a conference, which is different again from a note to an account you have sold to for a decade. Most vendors still send the one reasonable email.

    If you are writing to twenty utilities rather than two thousand, being right about each one is affordable.

    AquaIntel drafts the approach where the context lives, from what this utility has been arguing about, what it has already tried, who is on the map for this purchase, and what you actually offer. Sequences, not single sends. The mail leaves from your domain.

    You have a short list. You have outbound infrastructure. You intend to keep it.

    You already have, or want, ten or twenty accounts worth knowing. You own deliverability, domain reputation, and consent, and you are not handing them to anyone.

    Not for

    • Buyers who want AquaIntel to run the sequences as the sender
    • 500-account cadences
    • Open-rate bragging

    The job, as it exists today

    Someone opens the account. Someone opens five tabs. Someone writes an email that could have gone to any utility in the state.

    The context existed, in minutes, in CIP lines, in a conference badge, in last year’s install, and it never made it into the letter. So the letter gets ignored, correctly.

    Writing twenty good ones by hand is possible. Writing them every week, as boards meet and clocks move, is the part that falls off the desk.

    WHAT THE WORKFLOW DOES

    Not automated outreach. Drafting from context.

    Screening and contacts sit underneath it. We draft. You send, from your own inbox.

    1. Holds utility context and seller context in the same place

      What the record says, what your CRM says, what you sell.

    2. Drafts the approach pitched at this relationship state and this moment

      First contact, conference follow-up, or decade-old account. Different letters.

    3. Drafts sequences, not single sends

      A first email going unanswered is the normal case, not a failure.

    4. Hands the draft to your outbound stack

      The finished action is the draft in your system. The send is yours.

    What lands on the desk

    What lands is a sequence the salesperson can stand behind,

    about a plant they could describe without opening a tab.

    CONTEXT IN, DRAFT OUT

    Illustrative utility · your outbound tool

    1. Utility context · from monitoring

      Board has argued about lift-station odour complaints for two years. Chemical dosing trial ended in March. CIP line open, unscoped.

    2. Relationship state · from your CRM

      Your rep met the collections supervisor at the state conference in May. No prior sales to this district.

    3. What you actually offer · your product

      Odour-control units with a reference install two counties over, same sewer geometry, same dosing history.

    A three-touch sequence, in your outbound tool

    Touch 1
    The conference follow-up. Names the March trial. Offers the reference site, not a demo.
    Touch 2, +9 days
    One page on why dosing alone plateaued in the reference district.
    Touch 3, +3 weeks
    Short note timed to the next board meeting where the CIP line is up.
    Who sends
    Your rep. From your domain. In your stack.
    AquaIntel sends
    Nothing.

    What this is not.

    One rule above the others. Six things we will not do, and why.

    • It does not send anything

      Full stop.

    • Deliverability, domain reputation, and consent stay in your stack

      They are yours. They should stay yours.

    • A company that starts sending mail on other people’s behalf has quietly become a different company

      Same instinct as not becoming the CRM.

    • We do not become your CRM

      The draft lands in the system your team already uses.

    • Drafts for ten or twenty, not campaigns for five hundred

      Being right about each one is only affordable at that size.

    • Alert is not deliverable

      A draft someone can send is.

    Where this sits in the loop

    All solutions

    1. Screen

    2. Monitor

    3. Map the room

    4. Clocks

    5. Draft

      • This page

    6. Catch the bid

    7. Fit-check

    1. Screen

    2. Monitor

    3. Map the room

    4. Clocks

    5. Draft

      • This page

    6. Catch the bid

    7. Fit-check

    Questions we get on every call

    WHAT YOU GET ON A CALL

    Record, draft sequence, handoff into your tool

    A walkthrough with no AquaIntel Send button in it. Illustrative utility, not a named customer. No self-serve plan. No trial seat dump.

    1. The record

      What this utility has been arguing about and trying

    2. The draft sequence

      Pitched at this relationship state, this moment

    3. The handoff

      Into your outbound tool, from your domain