Scope of work, months one to twelve
Quick Transfer Moving and Storage
What we will do, month by month. What we need from you to do it. How leads are handled, and what gets measured and reported.
- Prepared for
- Ralph Mueller, President
Bob Allan, CFO
- Prepared by
- David Matthies
Carolyn Matthies
- Revision
- 8 · 1 September 2026
- Period covered
- Twelve months
Your side
What this asks of your people
Everything we need from Quick Transfer, in one place, with the time it takes and when it is needed.
| Who | What | How long | When |
| Alpha | A CNAME change in your DNS, discussed with them directly | Under 1 hour | Week 1 |
| Ryan | Freight and 3PL: how the work comes in, how it is quoted, what wins it | 1 hour | Weeks 1–2 |
| Wilf | Sales process end to end, and the questions he asks to qualify | 1 hour | Weeks 1–2 |
| Christian | Storage and warehousing, including what the new building needs to justify itself | 1 hour | Weeks 1–2 |
| Ralph Mueller | Sitting in on the three interviews above, as you asked. Then a session of your own, deliberately last, once you have heard all three. Then one approval on the positioning before anything publishes | Up to 5 hours in total | Weeks 1–6 |
| Anyone else Ralph nominates | Any further people Ralph wants represented in discovery. Named at kickoff and added to the same allowance rather than on top of it | 1 hour each | Weeks 1–3 |
| Whoever handles your systems | Exporting the customer list, and access to the tools that hold your data: current CRM or booking system, analytics, Google Business Profile, review platforms. Administrative rather than technical | 1–2 hours | Weeks 2–3 |
| Bob Allan | Baseline revenue and booking figures for a comparable prior period | Under 1 hour | Week 3 |
| One nominated person | Working with us as we build and program the knowledge base, so it represents Quick Transfer rather than a generic moving company. Answering questions, correcting what we get wrong, pointing us at what we have not asked about | A few hours a month, as needed | Months 1–3, then a quarterly checkpoint |
| Ralph Mueller | On camera. The discovery sessions in weeks one and two are recorded, which costs no extra time, then one proper shoot once the positioning is approved. Filmed in batches, refreshed later in the year | Recording adds nothing to discovery, then half a morning | Weeks 1–2, then month 2 |
The total ask on your key people
Two conversations maximum, an hour each. A second conversation with someone comes out of that allowance rather than being added to it.
The nominated person is the one standing ask, and only for the first three months while the knowledge base is programmed. That file is what the whole system generates against, so somebody inside the business has to tell us what is wrong with it. Heavy in month one, light by month three, a quarterly checkpoint after that.
Ongoing, after discovery
One monthly review call, roughly an hour, with Ralph and whoever else he wants in it. Timely access to booking and revenue records so measurement stays honest. A quarterly knowledge-base checkpoint, about an hour, to keep the system current as the business changes.
Months
Deliverables, month by month
Every month is listed on its own. Months one and two are onboarding: the system is built, programmed and connected before anything publishes. From month three the publishing rate holds and the topics are chosen by measurement rather than decided in advance.
Weighting: 3PL warehousing first, including household goods storage. Then local household moving, then long distance household moving. The verticals are built out sequentially in that order rather than all at once: each one gets a month of concentrated depth before the next begins, and once built it keeps running. Month four is vertical one, month five is vertical two, month seven is vertical three.
The article count rises through the year on purpose. The foundation is built in months one and two and then keeps deepening as the system learns from the intelligence it gathers and from your team's corrections. Output rises with it, because volume written against a shallow foundation is volume that does not sound like Quick Transfer. Social posts and guides hold at a steady rate throughout; only articles ramp.
Nothing is deployed without a testing cycle. Every new surface, integration and automation is tested before it goes live, and every content stream is proofed against a real published page before it runs at volume.
01Month 1
Onboarding, part one
Learn the business, install the system, and measure it before we touch it
Nothing publishes this month. A baseline taken after work begins makes the work look smaller than it is.
- Discovery interviews with Ryan, Wilf and Christian, per the table above, with Ralph sitting in.
- Ralph's own session, last. An hour, in week three, after he has sat through the other three. Where the business is going, what the year has to prove, and what he heard in those rooms that he had not heard before. It is scheduled at the end on purpose: the most useful things an owner says about his own business are usually the ones he thinks of while listening to his people describe it.
- Discovery filmed. The same sessions are recorded on camera. It costs no additional time and it captures your people talking about their own business unrehearsed, which is the most credible footage that will ever exist of Quick Transfer. Nothing is published without your say-so.
- Process map. How an inquiry becomes a booked job, where it stalls, who touches it. Separately for 3PL, local and long distance, because they do not behave the same way.
- Baseline AI visibility report against qtmoving.com. How the major AI answer engines describe Quick Transfer today, what they get wrong, and where they name a competitor instead. Dated and archived so month twelve has something honest to compare against.
- Marketing and messaging audit. Current site, listings, collateral and social read for what they claim, what they prove, and where they contradict each other.
- Technical and access inventory. Domain, DNS, hosting, CRM, analytics, Google Business Profile and Search Console. What exists, who controls it, what is broken.
- Sales baseline agreed in writing with Bob, using the most complete comparable period available, accounting for seasonality.
- AI CRM installed. The twelve tools in the package are set up and configured against Quick Transfer's own business rather than a template. At a high level they cover lead capture and qualification across voice, chat and web; the CRM that records and scores every interaction; nurture sequences by email and text; review generation and response; listings and local presence; content generation and publishing; and the reporting layer that ties them together. The full inventory, with what each one does and how it is configured for you, comes with onboarding.
- Brand profile built. Roughly sixty fields covering positioning, audience, offer, proof, voice and constraints. This is the file every piece of content is generated against, which is why the interviews come first.
- Knowledge base, first programming pass. The interviews, your existing collateral, your pricing logic, your service areas and your objection handling are turned into structured records the system reasons over. This is the single biggest determinant of whether the output sounds like Quick Transfer or like a generic moving company.
02Month 2
Onboarding, part two
Fix identity, connect everything, and prove the pipeline on a real page
Publishing content for a business the engines cannot reliably identify wastes the content, so identity comes before volume.
- Positioning and messaging document, approved by Ralph before anything publishes in it. Distinct positioning for 3PL, moving and storage, one voice underneath.
- Knowledge base, second programming pass, worked through with your nominated person. Gaps found in month one get filled, wrong answers get corrected, and the tone gets tuned against real examples of how your people actually talk about the work.
- Writing voices built. Separate voices for freight buyers, household movers and institutional clients, so a 3PL post does not read like a moving-day post. Same brand underneath, different register.
- Entity and identity pass. Consistent name, address and phone across listings, structured data on the site, Google Business Profile corrections, listings audit.
- Website live on your domain. The site is built on and hosted by our platform, so going live is a CNAME change in your DNS rather than a migration. Email, DNS control and everything else Alpha manages stays with them.
- AI crawler visibility enabled, so AI systems can read your pages rather than an empty shell. A further reversible DNS-level configuration, handled in the same conversation with Alpha. Nothing changes for a human visitor.
- Web chat agent live on the site, answering from your knowledge base rather than a script, qualifying by line of business and handing off to a person with the conversation attached.
- Your customer list imported. Loaded into the CRM, deduplicated, segmented by line of business and by recency, with source attribution set so every future inquiry can be traced to what produced it.
- Six social profiles claimed, optimized and connected. Facebook, Instagram, LinkedIn, Google Business Profile, TikTok and X. Consistent naming, correct categories, complete bios, service areas, hours, links and imagery, then connected for direct publishing.
- Google Search Console and analytics connected, so search demand and site behaviour are measured from month two rather than reconstructed later.
- Citation target list. The third-party sites AI engines actually cite for moving, storage and freight queries in your markets, and which of them already carry Quick Transfer.
- Lead routing live and tested, per the operations section below.
- Publishing pipeline verified end to end on a real page, on your real domain, read back by a real crawler.
- Ralph on camera. One shoot, half a morning, filmed in batches once the positioning is approved so the message is settled first. A named, visible president is one of the few things a competitor cannot copy, and it is what turns a moving company into a specific moving company in both a buyer's mind and an engine's. It goes live with the site rather than four months after it.
- Weekly AI visibility scans begin. From here the measurement runs on its own every week, whether or not anyone asks for it.
03Month 3
Publication begins
Full publishing rate, weighted to 3PL warehousing and storage
- 100 social posts, across all six platforms, each written for its platform with original imagery.
- 4 destination guides. Deep, researched pages on the places people move to and from, built to be the best answer on the internet to a real relocation question.
- 8 articles, answering the questions your buyers actually ask, chosen from measured gaps.
- Website depth begins. The site that went live in month two starts growing: the service pages for the first vertical get built out properly, with the structure and the internal linking an AI engine needs to understand what Quick Transfer does.
- Knowledge base, third programming pass. By the end of this month it is dialed in. From here it needs a quarterly checkpoint rather than ongoing involvement from your people.
- Remediation work begins. The specific fixes the measurement says will move the score: schema and structured data, FAQ blocks against real buyer questions, entity corrections, internal linking, and pages that exist to be cited rather than to be pretty.
- First citation submissions against the target list, tracked individually with status and outcome.
- First comparison report. Month three is the first point where movement against the baseline means anything.
04Month 4
Vertical one
3PL warehousing and household goods storage, in depth
Your first priority gets built out completely before the second one starts. Both buyers who fill the same building are covered here: the commercial and institutional accounts that take space on contract, and the household customers storing between moves or during a renovation.
- 100 social posts, 4 destination guides, 12 articles. The article count rises as the knowledge base gets deeper and the measurement gets more specific about what is worth writing.
- Full service and service-area page set for warehousing, 3PL and storage, covering the lanes and regions the business actually serves, each addressed by its place rather than by a headline.
- Institutional and government content, written for how a tender-writer or facilities manager actually evaluates a supplier.
- Competitor intelligence, per query. Who the engines recommend instead of you on warehousing and 3PL questions, and what those competitors have that you do not. This drives the following month's topics.
- Competitive positioning analysis, evidence-cited, on how Quick Transfer is placed against the named alternatives in freight and warehousing.
- Review generation live. Requests going out automatically after a completed job, responses drafted for approval, reviews feeding back into what the engines can see.
- Placement follow-through. Chasing submissions, correcting rejections, adding new citation sources as they appear in the data.
05Month 5
Vertical two
Local household moving, in depth
- 100 social posts, 4 destination guides, 15 articles.
- Full service and service-area page set for local moving across the neighbourhoods and communities you serve, built the same way the first vertical was.
- Second video batch, now that three months of measurement show which of the month-two pieces people actually watched and which questions they arrived with. Same format, half a morning, aimed rather than guessed.
- Seasonal build-ahead. Moving demand is sharply seasonal, so the summer peak content is written and staged now rather than published into it. From here the calendar runs ahead of demand rather than behind it.
- Share of voice tracking across the engines: what proportion of the answers on your buyer questions name Quick Transfer, and how that is trending.
- Engine change detection. What an AI engine started saying about you, and what it stopped saying, scan to scan. This is where a wrong claim gets caught before it hardens.
- Social listening live, watching your market, your competitors and your category for things worth responding to the same week rather than the next quarter.
- Second AI agent live: after-hours inquiry handling, so a 9pm inquiry is qualified and logged instead of lost until morning.
06Month 6
Half-year review
Judge it properly, then reforecast
The rate does not drop because it is review month. Publication continues at full volume throughout.
- 100 social posts, 4 destination guides, 20 articles.
- Written half-year review against the month-one baseline. What the engines say now versus then, what was published, what was submitted and accepted, what the sales figures did over the same period, and what we got wrong.
- Profit gap analysis. Where revenue is being left on the table across the three lines of business, based on six months of measured demand rather than assumption.
- Retention analysis on your existing customer base, since a repeat commercial account is cheaper than a new one and the list is already in the CRM.
- AI workforce expansion. The agents that earned their place get more to do; the ones that did not get replaced.
- Reforecast. Volumes, weighting and the priority order revisited against six months of evidence, in writing.
07Month 7
Vertical three
Long distance household moving, in depth
- 100 social posts, 4 destination guides, 22 articles.
- Origin-city pages, built for the cities your inbound long-distance business actually comes from rather than the ones you would guess. This is where the destination guides and the service pages start reinforcing each other.
- Full service page set for long distance, completing the sequential build across all three priorities.
- Customer proof captured and published. Real jobs, real outcomes, gathered as they happen and turned into content instead of remembered vaguely a year later.
- Short-form video at volume for the platforms where it outperforms static, using your own footage and the Ralph pieces filmed from month two onward.
- Website conversion depth. With three verticals published there is enough traffic to fix what happens after somebody arrives, not just how they get there.
08Month 8
Third-party authority
Get named on the sites the engines already trust
- 100 social posts, 4 destination guides, 25 articles.
- Citation placement expansion. Industry associations, freight and logistics directories, regional business media, and the niche sites that carry disproportionate weight in AI answers for your categories.
- Press and announcement distribution on anything genuinely newsworthy: the new building, a contract win you are able to name, a capability launch.
- Category news response. When something moves in freight, logistics or relocation, Quick Transfer has a published point of view on it while it is still being searched for.
- Domain authority and crawlability audit, re-run against month two, with the fixes actioned rather than listed.
09Month 9
Widening the front
Turn up what the data proved
- 100 social posts, 4 destination guides, 28 articles.
- Residential turned up if capacity has freed, weighted to the moves that are actually profitable rather than the ones that are merely available.
- Geographic expansion into the adjacent markets the visibility data shows are winnable, rather than the ones that look good on a map.
- Additional platforms where the measurement justifies them, added to the original six rather than replacing any of them. Nothing gets added on the grounds that it exists.
- Board-level summary for Ralph: one document, defensible numbers, suitable for showing a lender, a partner or a buyer.
10Month 10
Daily cadence
An article a day, sustained
- 100 social posts, 4 destination guides, and roughly 30 articles: one a day. This is the rate the first nine months were building the foundation to support. Publishing daily into a knowledge base that is not dialed in produces daily mediocrity, which is why it arrives here rather than in month three.
- Full remediation sweep, re-running every check from month one against the site as it now stands.
- Seasonal build-ahead, second cycle, staging the next peak before it arrives.
- Website structural review. Ten months of published pages need their architecture revisited so depth reads as authority rather than as accumulation.
11Month 11
Consolidation and year two
Hold the rate and build the plan for next year
- 100 social posts, 4 destination guides, roughly 30 articles.
- Attribution reconciliation. Every piece published against a measured gap, matched to what the engines did afterward, so the year-one number is built from records rather than assembled at the end.
- Year two projections, built from twelve months of your own measured data: what the trajectory says the next year produces if the rate holds, where the remaining gaps are, and what they are worth.
- Year two plan, drafted from what twelve months actually showed rather than from what looked sensible at the start. Verticals, markets, volumes and priorities, ready to discuss rather than ready to invent.
12Month 12
The verdict
Judge the year honestly, in writing
- 100 social posts, 4 destination guides, roughly 30 articles. The rate does not drop because it is review month.
- Year-one review. A written comparison against the month-one baseline covering how engines describe and cite the business, everything published, everything submitted, and what the sales figures did over the same period, with the things that did not work named as clearly as the things that did.
- Recommendation for what comes next. What to change, what to stop, and what year two should target, set against the projections from month eleven.
Volume
What gets published
Four workstreams, all beginning in month three once identity, the knowledge base and the pipeline are in place. They behave differently and should not be read as one number.
Social content
Posts produced and published to Quick Transfer's own accounts, each written for its platform rather than copied across them, with original imagery. Weighted to 3PL warehousing and storage first, then local household moving, then long distance.
100 posts per month, every month from month three.
Platforms: Facebook, Instagram, LinkedIn, Google Business Profile, TikTok and X. The mix is weighted by audience rather than spread evenly, since the platforms that reach 3PL buyers are not the ones that reach household movers.
Destination guides
The heaviest single piece of content we produce. Each one is a deeply researched page on a place people move to or from, running several thousand words, built from live research across the things a mover actually needs to know rather than from a template. These are the pages that earn a citation in an AI answer, because there is nothing thinner on the internet that answers the question better.
4 guides per month, every month from month three.
Articles and service-area pages
In-depth pages on your own website answering the questions your buyers actually ask, plus service-area pages for the places you serve, each addressed by its place rather than by a headline.
Ramping to one a day. Roughly 8 in month three, rising through the year to about 30 a month by month ten and held there. The ramp is deliberate: an article a day written against a knowledge base that is not yet dialed in produces a great deal of content that does not sound like you.
The website itself
The site goes live in month two and then keeps growing for the remaining ten. Service pages and service-area pages are built out vertical by vertical in the priority order, then the structure, internal linking and conversion paths are deepened as traffic arrives and the measurement shows what people do when they get there. A website that stops changing the week it launches is a brochure. This one is the surface everything else points at, so it is treated as a workstream rather than a milestone.
How each month's topics get chosen
The volumes above are minimums. The topics are not a fixed list decided in advance, and that is deliberate. Four inputs choose them each month.
The visibility gaps. The cities, buyer questions and search terms where an AI engine answers without naming Quick Transfer and names a competitor instead.
Competitive differentiation. What the named alternatives claim, what they cannot claim, and where Quick Transfer has something real that nobody is saying out loud.
Market intelligence. Continuous monitoring of your category, your competitors and your markets, so a shift in freight, logistics or relocation reaches the content while it still matters.
What is moving right now. Topics gaining traction in your industry get answered while they are being searched for rather than three months later, and seasonal demand is written ahead of the season rather than into it.
It is why the topics are not listed twelve months out. The ones worth writing in month eight get chosen by what months one through seven measured.
Operations
How a lead gets handled
Every step from arrival to outcome, and who owns each one. Built so no lead depends on somebody remembering.
01Inquiry arrivesSystem
By form, chat, phone or social. Captured with its source, so we know which content produced it.
02Sorted and qualifiedSystem
3PL and storage, local moving, or long distance.
03Routed to a named personSystemName supplied by you
By line of business, timestamped on arrival.
04First contact attemptQuick Transfer
Logged, with time to first contact measured.
05Outcome recordedQuick Transfer
Quoted, booked, lost, or no response.
06Nothing goes quietSystem
Anything uncontacted after an agreed window is escalated by name in the weekly summary.
What Quick Transfer needs to supply is one name per line of business, and a response-time expectation you are comfortable being measured against. Everything else is ours to build. The monthly report shows leads received, time to first contact, and outcome, side by side, because those three numbers together are the only honest way to tell a lead-generation problem from a follow-up problem.
Measurement
What gets measured and reported
The full list of what is measured and reported. Most of it updates weekly rather than monthly.
Whether AI engines know you and name you
| What we track | What it tells you |
| Does AI know who you are | Whether the engines can identify Quick Transfer correctly at all, and what they get wrong |
| How AI talks about you | The actual language the engines use, quoted, not summarized |
| Engines naming you | How many of the major engines name Quick Transfer on your buyer questions |
| Citation presence | Whether you are named as a source, and on which specific questions |
| Who gets recommended instead | The competitors named in your place, counted per answer |
| Share of voice | What proportion of answers on your buyer questions belong to you |
| Share of your namings | Which engines are carrying you, so a single-engine result is never read as a market result |
| What is changing | What an engine started saying and stopped saying, scan to scan |
| Visibility over time | Every measurement we have ever taken for you, on one line |
| The components of your score | The separate dimensions the visibility score is built from, each scored, so a number never moves without a reason |
| Signal strength | How strong the underlying evidence is, so a thin result is not presented as a firm one |
| What we asked on your behalf | The real buyer questions the whole score is measured on, listed |
| Where AI sends people | Across every answer collected, how often the link offered was yours and how often it was somebody else's |
| Openings we found | Questions in your market nobody is answering well, which become next month's work |
Search, site and what happens when someone arrives
| What we track | What it tells you |
| What people searched to find you | Real Google search terms that showed your site, with clicks, impressions, click rate and where you ranked on each |
| Published footprint | What exists on your domain that did not before, and whether engines can actually read it |
| Site performance | Load and render speed measured on a real page, phone and desktop separately |
| Conversion readiness | Contact form, live chat, online booking, phone visible, reviews shown, secure connection, payment. Each one present or missing, because a missing one is a visitor with no way to act |
| Domain authority and crawlability | Whether the technical foundation is helping or holding the content back |
The content itself, and what it did
| What we track | What it tells you |
| Published | What went out, where, and when |
| People reached and impressions | Audience size, per platform |
| Interactions | What people actually did with it, not just how many saw it |
| Best performing content | Ranked by engagement rather than by reach, because reach is buyable and engagement is not |
| What our work moved | Each piece published against a measured gap, matched to what the engines did next, including how fast |
| Placement submissions | Every third-party submission, with status and outcome, tracked individually |
| Remediation queue | What we are fixing, ordered by what moves the score most |
The sales side, in plain numbers
| What we track | What it tells you |
| Leads received, by source | How many inquiries arrived and which content produced them |
| Time to first contact | How long a lead waited, by line of business and by person |
| Outcome | Quoted, booked, lost, or no response |
| Lead to customer conversion | What proportion of inquiries became paying work |
| Revenue against baseline | Your own numbers against the month-one baseline agreed with Bob |
What arrives, and when
Weekly: an IQ Report on how the engines describe and cite Quick Transfer.
Monthly: the full written report within five business days of month end, and one review call.
Decisions
Three things we need decided before month one
Each one blocks or shapes delivery, so it is named here rather than discovered in month three.
- Which domain we publish to. Content accrues to the domain it sits on. Publishing to qtmoving.com now and redirecting later if the company moves is cheaper than waiting, and a move should be handled as a migration with redirects so the value carries across.
- Data residency for your Government of Canada work. You told us none of your data may be stored in the United States, and that US hosting would rule you out of those RFPs entirely. We are treating that as a condition to satisfy up front rather than a question to answer later. Three things have to be established and two of them are ours: where your website content is served and stored, where your CRM holds contact data, and what our own platform holds on your behalf. A written inquiry is open with the CRM vendor and we have been directed to their security team for a documented answer. We will not state a hosting region or a residency position for any of the three until each vendor has confirmed it in writing, because in government procurement those statements are read as commitments. What we need from you is the exact wording of the requirement, so we are answering the question you are actually asked rather than our version of it.
- One named person per line of business to receive leads, and a response-time expectation you are comfortable being measured against.
Listed so nobody assumes otherwise in month two. Any of it can be discussed as separate work.
- Paid advertising, on any platform
- Email campaigns to your existing customer list
- Sales training or sales process implementation
- Print, broadcast or event marketing
- The AI-native warehouse management system and the Relo prospecting engine, both scoped separately
Working together
Who does what
David Matthies
Builds and operates the system. Strategy, the discovery interviews, technical implementation, coordination with Alpha, and everything the platform produces and publishes. Your point of contact for the work itself.
Carolyn Matthies
Operations, marketing and the account relationship. Scheduling, reporting, and making sure what you asked for is what you are getting. Your point of contact for anything about the engagement rather than the technology.
Both of us are involved throughout rather than handing off after a launch. David is on every monthly review call. Between calls either of us can be reached directly, and anything technical or urgent goes to David.
FreshThink LLC
[email protected]
This page is kept current, so the link you have always shows the latest version.
Revision 8 · 1 September 2026 · For discussion.
Earlier revisions are available on request.