Written Scope: Fractional CMO, Set Up for Pursuits
Sample
- Prepared for
- A 25-person civil engineering firm in Sugar Land, Texas (fictional)
- Their team
- Three principals, four project managers, a proposal coordinator, and the engineering and survey staff
- Lead
- Joe Zeng
- Version
- 1, approved by both sides before work starts
1. The Goal
Why It's Here
Panels and developers decide, so nobody can promise a win. You get the work in writing and both numbers in every monthly report.
Win more work beyond your two biggest developers. Get on more public shortlists in the markets you choose, stop spending principals' hours on pursuits you can't win, and know who you know at every target. See it all on one page each month.
What we're working toward: a shortlist on at least 4 of every 10 public submittals in your chosen markets by Month 6, up from about 3 in 10 last year, and revenue from your top two clients down from about 64% last year to under 50% by Month 12. These are targets. We commit to the work below, and the report shows both numbers every month.
2. The Work
Why It's Here
Every line here is something a principal can check in the CRM or the report. Nothing vague made the list.
- Pursuit CRM
- Every pursuit and every relationship in one CRM, in your firm's own account: public submittals from the go or no-go call to the result, and private proposals from the first developer conversation to the award.
- SOQ library
- Current resumes for everyone you put forward, a project sheet for every project worth citing, and firm boilerplate, in one place. Anything used in a submittal gets updated within 5 business days after it goes out.
- Project pages
- A page on your website for each project worth citing: the client type, the scope, the constraint, and the outcome. Two a month, each approved by the project manager who ran it.
- Target list
- 30 targets: public owners, primes, and developers, each with a named relationship owner at your firm and the date of their last real conversation.
- Go or no-go checklist
- A written checklist your principals use on every public RFQ and every private proposal request, before anyone starts writing.
- Proposal follow-up
- Every private proposal gets a follow-up date in the CRM, and we draft the follow-up for the principal who sent it. No proposal sits unanswered.
- Shortlist interview prep
- For every shortlist, we help your team plan the story, the people, and the project examples, and run a practice round.
- Debriefs
- After every decision, win or lose, we draft the debrief request and write down what the panel or the developer said.
- Monthly pursuit report
- One page by the fifth business day of each month, covering the month before: public submittals, shortlists, and wins by owner, private proposals and awards, relationship coverage, the share of revenue from your top two clients, and what's stuck.
3. What We Don't Do
Why It's Here
Your engineers' judgment is what a selection panel scores. It stays with them, and we make sure it's seen.
We don't write your technical approach or stamp anything. Your engineers own the engineering. We keep the material current, edit and format submittals when you ask, and make sure the right people see your work.
We don't give legal advice on procurement rules. Selection rules differ by agency, so each agency's current requirements get confirmed with that agency before a pursuit.
4. The Go or No-Go Checklist
Why It's Here
A written check keeps principals' hours on pursuits you can win, and the record shows which passes were right.
Your principals answer these six questions on every public RFQ and private proposal request, in the CRM, before anyone starts writing. Two or more noes means pass, unless a principal writes down why not.
- Do we know the client, and does someone at the firm own the relationship?
- Is it in a market we chose in the plan?
- Do we have recent, similar projects and the people to put forward?
- If we'd team, is the prime one we know and trust?
- Can we staff the work if we win, without pulling people off current projects?
- Will a principal make time for the interview or the developer meeting?
Sample checklist. Yours is written with your principals in Month 1.
5. Private Work: Proposals and Developers
Why It's Here
Developers rarely issue RFQs. Counting proposals, awards, and new conversations shows whether work beyond your top two is growing.
Private land development comes from developers who already know you, so the report counts it the way the work arrives: proposals sent, awards, and new developer conversations. The goal is more developers who call you first, so no two clients carry most of the firm.
- Proposals sent to developers, each with a follow-up date.
- Awards, and which developer each one came from.
- New developer conversations: a principal or project manager met a developer you haven't worked for.
- Revenue from your top two clients, as a share of the total, from your accounting each quarter.
6. MUD Work: Relationships, Not Submittals
Why It's Here
Boards rarely switch engineers, so a submittal count would mislead. We track the developers who bring an engineer to new districts.
A developer usually brings its engineer when a new district is created, and a sitting board rarely switches. So MUD work here is relationship coverage, not RFQ submittals: which developers plan new districts in your area, who at your firm knows them, and when you last spoke.
The districts you already serve stay with the principals who serve them. The report counts them so the list stays honest, and nothing in this scope reaches out to another engineer's board.
7. Public Work and Teaming
Why It's Here
Certifications and teaming decide who a prime calls. Tracking them keeps your firm on the teams you want.
- TxDOT work starts with precertification in the work categories you perform. We track which primes pursue which work, and make sure they know your team before they build theirs.
- On TxDOT's federally funded work, primes often look for DBE subconsultants, and state agencies ask primes for a HUB subcontracting plan. If your firm holds HUB or DBE certification, it goes in every packet to primes. If it doesn't, we list certified partners for your own pursuits.
- Program rules change. Confirm the current rules with each agency before a pursuit. This isn't legal advice.
8. The Target List
Why It's Here
Relationships kept in one principal's head leave when they do. A named owner and a date keep them with the firm.
30 targets: public owners, primes, and developers, picked with your principals in Month 1. That means the developers planning new subdivisions and districts, the cities and counties you work in, and the TxDOT primes you team with. Each one gets a named relationship owner at your firm in Month 1, and a target added later gets its owner the day it joins the list.
The report shows which targets had a real conversation in the last 90 days, and which ones haven't.
Example number. Your list is as long as your principals can keep up with.
9. Who Does What
Why It's Here
Your principals own every client relationship and every go or no-go call. We keep the system that supports them.
Who does each part of the work: your firm or Apex Local Task Your firm Apex Local Client relationships Your firm: Your principals and project managers Apex Local: Never Go or no-go call Your firm: Your principals decide Apex Local: Keeps the checklist and the record Technical approach and stamps Your firm: Your engineers Apex Local: Never Developer proposals Your firm: Your principals write and send them Apex Local: Tracks each one and drafts the follow-up Resumes, project sheets, boilerplate Your firm: Your people review their own Apex Local: Keeps them current Submittal editing and formatting Your firm: Your proposal coordinator leads Apex Local: Edits and formats when asked Interview prep Your firm: Your team presents Apex Local: Plans the story and runs the practice round Monthly report Your firm: Reads it Apex Local: Writes it Joe Zeng leads the work and checks every line of the monthly pursuit report. AI drafts the first version. A graphic designer may help with project sheet layouts in Month 2: [Name], named in your scope before that work starts.
Backup: [Name], a specialist Joe works with, named in your scope before work starts, keeps the SOQ library and proposal follow-ups current if Joe is out.
10. Tools
Why It's Here
Your pursuit history is your firm's memory. It stays in your own accounts, where the next principal can find it.
- Your CRM
- HubSpot, or the CRM in Deltek Vantagepoint or Unanet if you run one. We work in whichever you have, in your firm's account.
- Your website
- Project pages go on your current site. No rebuild is planned.
- Shared drive
- The SOQ library lives in your SharePoint or Google Drive, in folders your team already uses.
- AI drafting tools
- Used for first drafts of project pages and the report, from your notes. This section lists each one that touches your firm's data, with its terms on training, before you sign.
Before setup, we check how your CRM and website connect and write it here. A piece that can't connect gets its workaround named.
11. Accounts and Data
Why It's Here
A principal who leaves shouldn't take the pursuit record along, so every account and file sits in the firm's name, not ours.
- Every account is in your firm's name: the CRM, the website, and the shared drive. A principal holds the admin logins, and we get user access.
- Resumes, project sheets, and proposals stay in your shared drive. We don't copy your SOQ library into our own systems.
- We remove our access within 2 business days of the work ending or your request, whichever comes first, and hand over the CRM setup and the target list with a one-page note.
- A written request has your data deleted from our own systems within 30 days. Otherwise our engagement record, the scope and each pursuit report, is kept up to 3 years after our last contact.
12. What a Person Approves
Why It's Here
Nothing about a project goes public until the person who ran it says yes. AI drafts, and Joe checks first.
- Every go or no-go call: a principal makes it.
- Every project page: the project manager who ran the project approves it. A client's name appears only with that client's OK.
- Every resume: the person it describes reviews it.
- Every proposal follow-up: the principal who sent the proposal approves it and sends it.
- Joe checks every AI draft before a principal or project manager reads it.
13. Dates
Why It's Here
Monthly steps with dates let a principal spot a slipping pursuit system long before Month 6.
- Month 1
- Review the last two years of pursuits and proposals. Interview principals about who they know. The CRM set up for pursuits. The go or no-go checklist agreed. The target list of 30, each target with a named relationship owner.
- Month 2
- The SOQ library in one place, with the resumes and project sheets from your last 10 submittals brought current. The first project pages live. The first monthly pursuit report, covering Month 1, by the fifth business day of Month 2.
- Month 3
- First review with your principals: keep, change, or cut each part of the work.
- Month 6
- Review against the goal: the public shortlist rate over Months 4 to 6, private awards, and the top-two share.
- Month 12
- The top-two share against its target, and the next year's plan written.
14. What Counts as Done
Why It's Here
The CRM and the checklist count as set up only once real pursuits and real opportunities have gone through them.
Setup is done when
- Every open pursuit and private proposal is in the CRM with a market and a go or no-go call.
- All 30 targets on the list have a named relationship owner.
- Each principal has been interviewed about who they know.
- Your principals have used the checklist on 3 real opportunities.
Each month from Month 2 is done when
- Every resume and project sheet used in a submittal was updated within 5 business days.
- Two project pages went live.
- Every open proposal has a follow-up date.
- Every shortlist interview got a practice round.
- The report reached you by the fifth business day.
15. Not in This Scope
Why It's Here
Shortlists and developers stay the focus because stamps, ads, and legal advice are named as outside the work.
Writing technical approaches, stamping or sealing anything, a website rebuild, paid ads, and legal advice on procurement rules. Any added work comes in through the change rule below.
16. Changes
Why It's Here
New markets wait for a principal's signature on the change, so the monthly report and the scope always agree.
Either side can ask for a change, such as a new market, a new owner on the target list, or interview coaching for a big pursuit. It's written here with its date, a principal approves it, and the work changes after that.
17. How Billing Works
Why It's Here
Month 1 sets up the pursuit system, and each month after it stands on its own.
Projects are a fixed price per phase. Monthly work is billed monthly. Any software you pay for is listed in your scope.
18. Terms
Why It's Here
Pursuits run long, but the contract doesn't: it earns each month, and the pursuit record stays with your principals.
- Month to month after the Month 1 setup.
- You can end it with 7 days' written notice, and Apex Local gives 30 days' written notice to end it.
- The CRM, the SOQ library, and every project page stay with the firm.
