Everything inside this line is yours.
Three key results and the roadblocks under them. Inside that boundary it is your sandbox: you own the outcomes, choose the approach, and make the calls. Martin supports on automation and approvals, and stays out of the day to day.
- Full autonomy. You sequence the work and decide when to clear a blocker, whether that is Meta verification, WhatsApp number config, or anything else. Prioritize and deprioritize as you see fit.
- The three roadblocks, yours. Martin builds the automations and holds approvals.
- One arena: GoHighLevel. Depth over breadth.
- Outcomes, not to-do lists. The KR table is the scoreboard.
- In-platform only. If it is not in GHL, it did not happen.
- Daily table hygiene. The ClickUp Objectives & Key Results and Roadblocks tables, under Steer in the Blueprint space. Checked every day, and eventually the seed data for the same view inside IQ Finance.
Your key results are your vesting schedule.
Up to 8,750 shares in reach, and every active key result now maps to a milestone. The reserve is not a mystery: one lever drives it, and two milestones you own outright feed that lever.
Unique people reached each day, in the platform. Breadth is the lever; the nurturing engine handles frequency.
After expenses, due September 30.
Diagnostics and partners are the two engines that generate real reasons to reach out. Grow them, and the daily reach that drives the reserve grows with them.
The other three milestones
First Full Implementation
A full build, not the $3,500 front end. Martin drives the offer, onboarding, and the Paraguay and Canada subcontractors; Tim's support through closeout vests it.
Approved Field Lane
A reusable playbook into one approved jurisdiction (Panama or similar, not Cayman): three vetted local partners, fee ranges, document checklist, readiness packet. Build once, run clients down it repeatedly.
Paraguay Partner Network
The in-person version: travel to Paraguay, personally secure three qualified partners. It overlaps M4's delivery search, which is why the subcontractor hunt starts now.
Milestones are binary and proof-gated. That is the real reason the work has to live in GHL and ClickUp: it is how completion gets evidenced and approved.
PDF Equity Vesting & Earn-Up Agreement 20 pages · up to 8,750 shares across 5 earn-up milestones ↗Where each one actually stands.
Measured against the live account today, not against intentions. Each card carries the proposed change to your ClickUp key result, and the gap that change exposes.
10 Contacts Messaged Per Day
The metric changed from total messages to unique contacts reached per day. Five people messaged once beats one person messaged five times, so a contact counts once a day no matter how many messages. Repeat touches are the nurturing engine's job, not this number's. Of 43 conversations today only 7 are real people, so treat the counter as near 0 and instrument it, because nothing measures this yet.
10 Strategic Diagnostics
One call (Carrie Lim) currently meets the qualification bar. Others in the pipeline are real prospects but do not yet count toward the equity milestone, either because no call was booked on an approved calendar or the CRM proof is incomplete. Milestone credit lands at 5; 10 is the sprint target. Supply is the constraint, with only 2 of 7 lead sources switched on.
New habit, starting now: mark every appointment Showed or No-show in GHL the day it happens. Nothing does this today, which is why completion cannot be read from the calendar. Do it consistently and this KR tracks itself.
30 Referral Partners, signed and managed
Billy Guan and Noah Gould are signed, nine more partner opportunities are in motion, and the agreements and acquisition agenda are done. But zero partners have a live referral cadence, which is the half that matters.
First Full Implementation to Closeout
The first client just closed on the $3,500 front-end offer. Real revenue, but the milestone vests only on a full Global Runway Build through active closeout, so the M4 clock has not started yet. Next move is converting this client, or the next, up into the full build.
These are suggested edits to the ClickUp key results. Nothing changes in the tables until you say go.
Torn down, line by line.
Every control scored against the live GoHighLevel account, the build documentation, and the communication-channel standard. Open one to see exactly what is done, what is missing, and how to close it.
45%Done
Multi-Channel Messaging InfrastructureRoadblock P2 · scored email-first · 13 controls
▶
| Control | Current state | Gap | How to close it |
|---|---|---|---|
| Email identities | Done. team@blueprintglobal.io as the human mailbox, team@mail.blueprintglobal.io as the automated sender, cleanly separated. | None. | — |
| Email deliverability | Done. SPF, DKIM, and DMARC pass on the dedicated sending domain, verified at build closeout. | Live status is not exposed by the API. | Spot-check once in GHL Settings → Email Services. |
| Default email service | Partial. The location has no default sending service selected (defaultEmailService is empty). | Sends may fall back rather than using the intended service. | Select the dedicated service in GHL Settings → Email Services. |
| Threading and reply continuity | Done. A controlled inbound test produced one conversation, one contact, no duplicate reply. | None. | — |
| SMS number | Partial. One Twilio number, +1 289-207-7737, Ontario, Canada. Voice, SMS, and MMS capable and set as default. | The entity is US (Wyoming) but the only number is Canadian, so US prospects see a foreign number. | Decide CA-only vs adding a US number in GHL Phone Numbers. Business call, not a config bug. |
| A2P registration | Not required. Canadian long code, so no US 10DLC brand or campaign is needed. Empty bundle is expected. | Becomes mandatory the moment a US number is added. | If a US number is added, register brand and campaign in GHL Trust Center first. |
| Opt-out handling | Unverified. Not exposed by the API. | STOP, HELP, and DND behavior unconfirmed. | Confirm in the GHL phone settings before any outbound SMS. |
| SMS consent capture | Partial. Two consent fields exist on the contact record (marketing and non-marketing). | No automation reads them, so consent is captured but not enforced. | Gate any SMS send on the consent field via a GHL workflow. |
| Unconfirmed. Set up on Aug 18, but no WhatsApp provider is visible through the API and no real message has ever been sent or received. | Cannot confirm it is actually connected and message-capable. | Verify in GHL Settings → Conversations, then send one real test both ways. | |
| Voice routing | Not configured. No forwarding number and no ring-all users, so an inbound call currently reaches nobody. | Any prospect who calls the number is lost silently. | Set forwarding or ring-all in GHL number settings. Fast fix, high consequence. |
| Voicemail and hours | Not configured as far as can be verified. UI-only. | No greeting, no after-hours path. | Configure alongside routing in GHL. |
| Send and receive proof | Missing. No documented end-to-end test per channel. | This is the evidence that turns "configured" into "trusted." | Outside GHL Run 3 to 5 test contacts per live channel and record the result. |
| Failure ownership | Not running. A monitoring cadence is defined but nobody owns it. | Delivery failures and route drift would go unnoticed. | Outside GHL Name yourself owner and add the check to the daily routine. |
20%Done
Contact IntelligenceRoadblock P3 · scored on the data · gates the daily-contacts KR
▶
| Control | Current state | Gap | How to close it |
|---|---|---|---|
| Intake schema | Done. 28 custom fields covering journey, residency, income, goals, consent, and lead source. | None. The structure is complete. | — |
| Form to field mapping | Verified working. Every field any human has actually submitted has landed on the contact record, on both intake forms. | None. An earlier "broken mapping" reading was a false alarm caused by low volume, not a defect. | — |
| Custom intake app | Proven in code, unproven live. The field mapping is correct and the health endpoint reports zero failed syncs, but no real external submission has come through yet. | The live HTTP path has never been exercised by a genuine submitter. | One deliberate test submission through the live form settles it. |
| Contact volume | 47 contacts. 40 of them were manually keyed into the CRM in a bulk load and carry only Journey and Lead Source. | The base is small and mostly un-enriched by origin, not by failure. | Volume comes from the outreach engine, not a config change. |
| Reachability | Thin. 51% have an email, 60% a phone, and 11 contacts have neither. | Roughly half the base cannot be reached on the primary channel. | Enrich or retire the unreachable records. Direct input to the daily-contacts KR. |
| Qualification depth | Sparse. Annual Income 13%, Primary Goal 4%, Tax Residence 2%, Residence Status 2%. | Not enough signal to target or prioritize outreach intelligently. | Capture on every new call, and backfill the live prospects by hand. |
| Lead source hygiene | Weak. 30 of 47 contacts have no source recorded at all. | Cannot tell which channels actually produce, which undercuts the diagnostics KR. | Stamp a source on every entry point and every manual add. |
| Segmentation | Unused. Three tags exist and zero contacts carry any tag. | No way to slice the base for a targeted campaign. | Define a small tagging convention and apply it via GHL workflow or import. |
| Working list | ~16 to 24 contacts are genuinely reachable and worth enriching. | That is the real denominator for re-engagement, not 47. | Build the list first, then run the manual campaign against it. |
10%Done
Outreach ExecutionRoadblock P4 · scored on the system · runs last, by design
▶
| Control | Current state | Gap | How to close it |
|---|---|---|---|
| Pipelines and stages | Done. Five pipelines covering customer, partner, subcontractor, CPA, and fulfillment. | None structurally. | — |
| Calendars | Done. Nine calendars, each mapped to the pipeline stage it feeds. | Appointments are not being marked Showed or No-show. | New daily habit, and the diagnostics KR becomes self-tracking. |
| Published automation | None. Zero published workflows. One sits in draft. | Nothing fires on a new lead, a booking, a no-show, or a payment. | Publish the three workflows below, once manual outreach proves the message. |
| Campaigns | None. No campaigns and no scheduled email exist. | No repeatable send motion. | Starts with the Blueprint Brief newsletter. |
| Manual vs automated rule | Undefined. No rule decides what gets personal attention and what gets enrolled. | This is the heart of the roadblock, self-rated 8.5 out of 10. | Outside GHL A written rule: who always gets a human, who gets a sequence. |
| Partner activation flow | Not started. Referral-engine subtask. | Needed for the "manage" half of the 30-partner KR. | Build after the first partners are re-engaged manually. |
| Partner nurture cadence | Not started. Bi-weekly sequence still to do. | Signed partners go quiet without a drumbeat. | Second workflow to publish. |
| Onboarding sequence | Not started. | A closed client has no automated path into delivery. | Third workflow. Feeds the first full implementation. |
Aim for a call. Fall back to a sequence.
Manual re-engagement into the warm and dormant base. Every conversation is trying to do one thing: get a booked call. Only when that is a no does the contact go into a standing workflow.
Get them on a call
A booked call is the outcome that moves every key result. Pick the calendar that matches who you are talking to and send the link directly in the conversation.
Enroll them in a workflow
Nobody exits the conversation without a next step. If a call is not on the table today, they go into one of three standing sequences so the relationship keeps running.
Manual first proves which message and which segment respond. Whatever lands then gets built into the workflow, and theme-based campaigns run on top as the situational layer. Automation scales a proven message, never an unproven one.
How the inbox runs while you build.
Component #2 of the five GHL considerations lives here in Part I, but framed as an outcome, not a configuration exercise: messages that provably send, arrive, and get answered. The operating standard is already written in the SLA document, and closing its one open workstream is the first thing that makes the account trustworthy.
The rule of the room
- Two accounts. The Team account owns routine inbound; Martin handles exceptions and declared backup. A mention asks for input; ownership stays with you unless deliberately reassigned.
- The rhythm. Check the Unassigned Inbound view at 10:00 and 15:00 ET each business day, then work the Team Needs Reply view. Monday to Friday, 09:00 to 17:00 ET.
- The bar. Urgent gets same-day acknowledgement and safe escalation. Standard gets acknowledgement in one business day and a real answer or next step within two.
- Done means done. A human reply, a documented no-response decision, or an explicit handoff. Marking read is not completion.
Your first moves to close the baseline
- Name yourself the queue operator and start the 10:00 and 15:00 checks with the monthly four-count log. This is the one open workstream gate in the whole build.
- Confirm assignment and mention alerts actually land on your desktop and phone.
- Hold the baseline for 30 days and 25 real inbound conversations before any native SLA, AI, or auto-reply switches on.
- Housekeeping: apply the three opportunity-card layouts in your own browser, and finish the Team-mailbox send-as check.