ECG internal, do not forward

Wednesday, three calls.
Andy at 2, Brad at 4, BOY at 6.

Wednesday, August 26, 2026 · UK times · prepared 12:00 from live reads
No pricing on this page.
14:00 ANDY + BEN 16:00 BRAD 18:00 BOY

00 Before 14:00

UKETCallMeetInvite state as at 10:50
14:0009:00Andy Ben Dan Connect (Andy Seaman, RMB Exchange; Ben Stammers on his personal Gmail)jkt-phbi-ztpBoth unanswered.
16:0011:00 (10:00 CT)Brad/Dan (Brad Nicolaisen, TotalTek)bbd-dnvz-quxBrad accepted 25 Aug.
18:0013:00BOY Machines test-week working session (Marko Koorneef, Brian Towler)zap-bymx-ufqBoth accepted. Brian will be driving.

Contacts: andy@rmb.exchange (mobile in your WhatsApp) · benjistammers@gmail.com / ben@digica.com · brad.nicolaisen@totaltek.com · mkoorneef@boymachines.com · btowler@boymachines.com. Numbers are on the internal sheet.

Three things to do first

  • Chase Andy and Ben for the 14:00. Neither has accepted and the morning Gap Check flagged it. One line each.
  • Move the solo "NETZZAR STRIPE" block. It still sits on 18:00-19:00 UK, exactly over the BOY call.
  • Laptop on mains for the whole BOY call. The voice poller and the daily run both stop on battery. Off mains, the 15-minute transcript loop dies mid-demo.

The gaps: 15:00-16:00, write the Andy decision-log entry while it is fresh (record the call; the commercial part of it exists nowhere else) and send the chases you owe. 17:00-18:00, BOY pre-flight: mains, Netzzar block gone, terminal in the engagement folder, the ADD/LEAVE workbook and the voice queue open. Also on the busenq calendar: a personal gym block 16:30-17:30, inside the Brad call.

Call 1 · 14:00 UK

Andy Seaman and Ben Stammers

JOIN MEET jkt-phbi-ztp ↗
The three-way owed since July. Ben introduced Andy in June, sat on the 17 Jul flight check, and on Tuesday said Andy is not proactive on the leads, sat on the Aviva risk and has no CRM. You told Ben in writing yesterday that you would come back this week with how you would set up the meeting-booking side. Commercials stayed off email, on purpose.
949
connection requests since 21 Jul, six campaigns ACTIVE
26%
accepted (248). UK C1 runs 38%, C2 and C3 about 21%
16+1
replies on the dashboard, plus one who messaged first. 5 classed interested, 2 unread
227
Singapore requests in 17 days, 1 scored reply, 1 unworked inbound
2,346
targets never touched. UK C1 has about 44 days of stock left
0
RMB records in the CRM. Signed PDFs sit only in Gmail

The two-minute version

The five threads to work, in order (who they are is on the internal sheet)

  1. Singapore, private-credit intelligence (SG C2). 24 Aug: asked outright to be told more about what we do. Unread. The Singapore test's only real bite. Andy answers him today: one sentence on what the platform does for a private-credit desk and one question back, no link.
  2. Aviva Investors, compliance lead (UK C3). 7 Aug happy to chat, 12 Aug sent a Teams invite for Friday 10am, Andy "Great, speak then." Silence since; the thread was re-read in full this morning and ends there. Two dozen or so other Aviva people are loaded across the UK campaigns and most have already had an invitation. If the Aviva conversation is live, ask Andy whether the remaining Aviva sends should hold until it lands (a gated write afterwards, not on the call).
  3. UK wealth consolidator, marketing director (UK C3). 19 Aug: a quick call, mid September. Andy: send a calendar invite. Ball with the prospect, no chase, six days. Does Andy send the invite, or do we.
  4. UK boutique, CEO (UK C2). 10 Aug: asked what the platform is. Andy replied with links on 10, 15 and 18 Aug. Silent since. A CEO who asked a buying question is a phone call, not a fourth link.
  5. Global asset manager, credit PM (UK C1). Not his role, and he named three buyer titles to go after instead. A routing map from inside a target account, never worked.

The portal's own five "interested" are the same four plus a founder who asked what we sell on 29 Jul and went quiet; the fifth above is on the list as a routing map, not as interest. Soft: a head of fixed income at a large manager said "I'll come back to you in September". Nobody has it diarised.

Run of the call

  1. Open on the numbers, one breath. Since 20 July: 949 requests out, 248 accepted, one in four. Sixteen replies on your dashboard and one more who messaged you first, so seventeen conversations, five of them warm. Singapore is 17 days in, accepts at the UK rate, one reply. Then the five-people line, then straight to the two unread ones.
  2. Aviva, 14 August: what happened. Then the Singapore reply: Andy answers him today. Then the mid-September call: does Andy send the invite, or do we.
  3. Put the desk on the table. Every reply answered the same day in Andy's voice, every warm one gets a next step in a diary, a Monday one-pager of where each conversation is, a CRM row per conversation (which also fixes attribution on the share). Copy fixes while we are in there: the brand confusion (Andy's own LinkedIn headline says EPIC Investment Partners, the sequence says Minerva and Athena, the links say x-trillion; a CEO stopped on 21 Aug to ask which it was; recommend one name on the seat, which one is Andy's call) and the "seven hours a week" study line a COO took apart on 13 Aug (retire it or re-source it).
  4. Ben's stake. Ask him, do not assume. Tuesday's transcript was garbled. If he names a number or a share you are not ready for: Noted. I'll cost the desk properly and the three of us get back on a call at the end of the week. I'd rather do the numbers live than in an email. Nothing is agreed on the call; anything agreed later goes in the decision log. Hold the 20% and move scope or timing, never a cheaper price for the same work: scope the desk to what the share buys, or start the desk fee at the first signed sourced client, or Andy carries third-party costs with the share unchanged. Do not offer "we'll do it out of the 20%" as a standalone option.
  5. Three quick decisions with Andy: connection notes on or off (he has Sales Navigator, the A/B is built and inert, C2 accepts at 20% against C1's 38%); Singapore scale, hold or stop (the 8 Aug rule was first reply or two weeks with none; withdraw rate is 54% of resolved invites against 25% in the UK); the Guinness fund-management idea from 24 Jul, which needs its own paper before anyone says yes.
  6. Own the two disclosures. Cap at 200 from the start, averaging about 180, and C3 live from day one. Say them before he finds them.
  7. Close on who does what by when. His Singapore dates; the terminal-seat anchor for Singapore (the UK pounds line went out to a Singapore prospect again at 07:58 UTC this morning; if he wants a Singapore-dollar figure, the number has to come from him, we do not convert it); hedge funds in or out; and the Aviva answer.

Numbers you may use, and nothing else

The brief locks the set: 15 seconds a chart, 20 to 30 minutes by hand, 4,000 bonds validated, 10,000 bonds a day, the terminal-seat line, seven hours a week. Client references stay "an established fixed-income asset manager" and "a global bond fund". Guinness and the Wealthy Nations Bond Fund are suppression entries, never proof.

Landmines

  • No vendor names. Andy asked in July to "find out how you do all this". Discipline level, "our platform".
  • Digica stays out while Andy is on. No Digica numbers, no seat-scope talk, no TotalTek.
  • Do not quote Tuesday's transcript at Ben. Let him restate.
  • The share is signed and survives termination. A loose sentence in a follow-up email can vary it. Keep any restructure verbal until you decide.
  • Andy's red line is handover, not money. His words on 17 Jul: "there's got to be some sort of sensible cut off... I want this to come through." Frame the desk as making sure conversations get worked.

If Ben stays on after Andy drops (Digica only, five minutes)

  • Søren's timing complaint from this morning: the watcher now polls round the clock, reads bursts as one reply, and stands down when Søren has already answered. Your reply to him is staged, unsent, Ben on Cc.
  • Ben owes you his example message texts, the niche pick from the HubSpot prompt, Jim's surname and email, and the tests doc.
  • Papering Digica for TotalTek is urgent (scope, cost, NDA) now that shape is twelve months, and you need Ben's written line on the US-border deployment claim already in sent copy.
  • Seat scope: six seats run, Jim makes seven, one more makes eight. Your call whether to raise it.

After the call

Call 2 · 16:00 UK / 10:00 CT

Brad Nicolaisen, TotalTek

JOIN MEET bbd-dnvz-qux ↗
This is the lock session your 24 Aug email called "Tuesday". No call happened yesterday: Brad accepted the Wednesday slot and declined the Tuesday one. Your 24 Aug email to Brad alone is the last written position. The one outcome: Brad's yes to the commercial shape so the revised proposal can be written and his recommendation to Brock and Sejal runs off one governed document. Everything else (NDA answer, his maritime documents, a Brock touchpoint, a real close date) serves that. You promised the revised document "the same day" in writing; it is not built and the builder has not been touched since 16 Aug.

Two things to have in your head

  • Open by asking, not assuming. Texts and calls with Brad are invisible here. "Anything moved since my email on Sunday night?" before you restate a position he may already have relayed to Brock. Whether Brock has seen the monthly option at all is not on record.
  • Heather is Heather Sullivan, Director of Marketing (demand-gen and ABM; the super user in the plan; owns the maritime ICP and the ZoomInfo counts). Her email is not on file; ask Brad for it with the NDA scope.

Brock's board (paraphrased; his own words are on the internal sheet only)

Cash first, capability and visibility second, speed to learning third. Ownership and security unranked. Decision still open on Brad's account of their 18 Aug 1:1; Brad is writing the recommendation. So the twelve-month run, the innovation-lab upskilling and the media package are the story. Ownership at month four is the safety net, not the headline. Do not open on Build, Run, Own.

His six questions, and where your answer already sits

Brock is askingYour 24 Aug answer
Validation tool, or a capability they own and improve?Build timeline unchanged, ownership completes at month four, months five to twelve buy operating, most of the cash behind the first evidence.
Is this an analyst-style authority platform, and what is that worth?"An analyst house rents you access to its audience on a retainer. We own the outlet... What we are not is analyst validation; we do not rate vendors and would not pretend otherwise." Hold it word for word.
Does it support the whole TotalTek brand, especially maritime?One brand layer across SAP, PMO, AI and maritime on a 12-month editorial calendar; practice lanes underneath; the maritime lane in from day one under the monthly option.
Does a separate AI brain duplicate what should live in their own knowledge estate?Hybrid. The CRM is the system of record for revenue; the brain is human-readable playbooks whose home is TotalTek's call at week one, inside their own Microsoft estate (never name the products). The execution layer is what we build.
Where does it sit in the sales process, who operates it?The unit owns everything up to the meeting; AEs take it from there; Heather as super user, the innovation lab from month four, the operator trained in the build. All named in week one.
What justifies the premium; can existing marketing spend fund it?Value the media on TotalTek's avoided spend, not our stated market value. The worksheet. Plus the cash profile.

Run of the call

  1. Where Brad is. Has Brock seen the 24 Aug positions, did anything land badly, what does his recommendation say today, what does he need from you to finish it. You asked Brad for avoided-spend numbers and the maritime documents; neither arrived. Ask again.
  2. Build the avoided-spend worksheet live, before any commercial mechanics. Your next-steps list says quantify the media on TotalTek's actual avoided or overlapping spend, not our stated value. Let's do that now, on your numbers. Left: what TotalTek spends or has budgeted on PR or comms retainers, content and design, paid placements, email distribution to bought audiences, social amplification. Right: what the package delivers at no charge, twelve monthly releases at Gold level or above, the eight-page feature and executive interview, the front-cover release, social behind every release. Anything the package does not do stays on their side; let him watch you refuse to net it. Say plainly that the cash structure stands on its own with no media value attached.
  3. Confirm the shape, cut to the three things that are new: the monthly option as an option alongside the unchanged four-month route, nothing repriced; maritime in from day one with no separate charge; months five to twelve buy operating and stop at twelve, ownership still completing at month four. The rest is SOW paper and belongs in the document. If the cash line comes back as "still too much": We don't cut the price for the same build, because the price is what funds the team and the operator that make it work. The monthly option already moves the cash curve. If that's still not the shape, we narrow the scope: the brain stays the separate module and the film comes out. Which of those is the real constraint? Scope and timing, never price.
  4. Maritime. Scope set in week one from Brad's solution document and Heather's ICP: the yard map, contract and tender monitoring with SAM.gov as a timing signal, AI scoring of yard fit, supplier-network mapping. Federal task orders stay out.
  5. NDA. Recommended position: yes, mutual, we draft it from the US template this week, scoped to cover the maritime documents and Heather's ICP. Settle it either way.
  6. What ships with the SOW: the Digica-led security pack, contract terms, the staffing and key-person note, cleared references, the platform agreements and owner-consent evidence via the direct intro. If Brad asks what Digica is to us contractually: the security and compliance partner on this engagement, at our cost, being papered alongside the SOW. Nothing more, because nothing more exists yet.
  7. Close on timing. Do not promise "today" a third time. You'll have the revised document in your hands before your recommendation goes to Brock. Tell me the date you're sending it and I'll be a clear day ahead of you. His recommendation date, whether a Brock touchpoint helps or hurts, the real close date (the CRM says 31 Aug), what "yes" looks like and who papers it.

Contradictions you are carrying into the room

  • The document Brock holds does not contain the offer you are locking. No monthly option, no twelve months, no run-phase definition, no first-party platform treatment. Your email pre-empts it. The revision is what closes the gap.
  • Maritime: the document says the dedicated lane is scoped and priced at the SOW; your email says in from day one, no separate charge. Brock asked for the cost treatment settled. Say the email version and put it in the document.
  • The seat line is "optional managed continuity from month five" in the document and a first-party platform cost from day one in the email. Same number, opposite mechanism. The 14 Aug evaluation once called it a "required" fee; say it exactly as the email says it.
  • "No ongoing fee" versus months five to twelve. The reconciling sentence: nothing after month four is a license, a fee for ownership, or a condition of keeping the build running; the invoices buy operating and stop at twelve.
  • The cash-at-first-evidence comparison is measured when the first cohort is reporting, the end of month two, not month one. Say "by the time the first cohort is reporting". If Brad adds up the twelve-month total out loud, the arithmetic is on the internal sheet: the monthly route costs more in total and buys eight more months of us operating the engine; its case is cash-at-risk timing, the full-term stop rule and the run. Do not volunteer the totals; do not be caught without them. The social add-on their own team asked for sits outside every total; say so if the all-in framing comes up.
  • The hub is stale (the repo copy still carries the 11 Aug proposal, week one 17 Aug, maritime cost "the one open commercial item"; the deployed copy was not readable this morning; a CRM note says zero views for four days, unverified). Keep it out of the conversation.

Landmines

  • Pre-signature audit. Every written claim gets proof-checked. Payer proof on the partner-funded media program cannot be produced; never offer invoices, source documents or NDA-gated evidence on the media. Defensible: card prices, ledger placements, the twelve-months-at-Gold maths, the two live busenq.com URLs, the Issue 144 claim.
  • No new figures, at all. Every number in play traces to a sent document or a panel read. Not on the internal numbers sheet, not said. Traps: the second-hand test budget, the aggregator revenue, 100+ seats, five to ten a week, reply-rate percentages, the media reach lines, and a per-seat figure under twenty dollars in a recap Brad holds (a transcription error; the real line is fifteen profiles at the platform's own rate).
  • Alta. Do not name it unless Brad does. If he does: concede the three-agent scope, do not attack their certifications, use the extra-vendor-inside-the-CMMC-boundary angle; the written assessment in section 7 already stands.
  • The telephony partner and an incident anecdote are in your 24 Aug email, against the no-vendor-names rule. Cannot be unsent. Do not build on it. If it comes up: no SMS, no automated calling, by design, TCPA exposure, human voice notes inside LinkedIn sequences instead.
  • Brad is not the decision maker and he is exposed. Brock decides, Sejal Shah is on the cover ("Prepared for" and nothing else about her). Friendly texts are not authorisation.
  • DIY temptation. Brad runs an AI lab and one of Brock's criteria asks whether they should operate it themselves. Add nothing to the paper beyond what the revision needs.
  • Nothing is authorised. A warm call is not a start date. Do not re-date the roadmap.
  • Say "profile", not "account", on the planning target. The maritime warm route stays unnamed. Both transcripts label Brad as "Thomas".

After the call

Call 3 · 18:00 UK / 1:00pm ET

Marko Koorneef and Brian Towler, BOY Machines

JOIN MEET zap-bymx-ufq ↗
Agree the targeting filters rep by rep, start the manager sandbox test week live on the call, set the two follow-on dates. The working-call pack is the script; this is what changed since it was written.
1,096
invitations sent this morning / 166 accepted / 54 replies. Hub shows 996 / 157 / 50, which is Monday's close
19
Zintis invitations on 25 Aug (Tom sent 18). 31 lifetime against zero before Monday. Fixed.
51/200
Brian's seat allowance used Mon-Tue. Tuesday's 26 went out 4 to 5 each across six of his seven campaigns. Not a cap.
12
items in today's edition, LinkedIn block back, Cc and Reply-To to you live on the first real send
2 of 5
reps accepted Monday (4 of 7 invitees with you and Marko). Outstanding: Justin, Nick, Zintis.
32 of 34
canary recoveries verified deliverable. ADD/LEAVE sheet ready. Nothing writes until it comes back.

The two-minute version

Run of the call

  1. Filters, rep by rep. Mike's two cases as the study set: North (a cull cannot recall a send) and Anaforian (a one-word headline "Motion" meant keep sending; he accepted, then read "Motion - Retired"). Say out loud: the keyword list ranks, it does not exclude; the screen reads the CRM title, the sweeps read the live headline, and they disagree; do-not-bulk-email (3,187 contacts) gates email, not LinkedIn. The one-sentence decision: does a one-word or empty headline mean keep and send, or hold for a human, at a cost of roughly 570 profiles out of circulation.
  2. Kim's portal login. Invite staged, unredeemed. Send it live if you rule today, walk her in, add her to the poller map when she redeems.
  3. Start the test week. Confirm the picks out loud (defaults: Marko gets Mike / Mid Atlantic, Brian gets Tom / North Central). Then, from the BOY engagement folder (cd there first, the scripts use relative paths): python voice/flip_voice_flag.py --on, confirm enabled true in the readback; then enabled true plus the picks in dailymail/test-editions-config.json. Reps see nothing this week. PR #59 stays unmerged. Tom's and Nick's invites stay held.
  4. Quote-desk walkthrough with Nadine and Sonia. A date. Their process, their ownership.
  5. Nick's sign-off. His word-for-word yes on the four messages, then your licence click. The activation script refuses to run until both are true.
  6. Monday 31 Aug, 10:30 ET, confirmed and invited (Meet bkf-dtfb-mdn). Kim on it or not. A clean test week keeps the date; 14 Sep is the fallback (7 Sep is Labor Day). Close with the day-by-day and who answers what if an edition looks wrong.

Fresh material you can say

  • Canary: 100 tried, 34 found, 32 verified at mailbox level (20 clean, 12 catch-all), about 1.1 credits per verified address. The ADD/LEAVE sheet is ready to show on screen; it is not staged as a send, so "send it now" is a gated send after the call. Say the trial result and hold the projection: The trial sizes the full run. I'll come back with the credit figure, and it needs a separate go from me before it spends. If Marko asks the price: It runs on credits. I'll confirm the rate and give you a number in writing. No dollar rate is recorded anywhere, so no dollar figure exists to say. Quote 2,947 remain / 2,781 solved, never 2,798, 2,930 or "plus 700 to 900".
  • Reactivation closed. 93 of 651 now active, every remaining inactive is flagged or ex-BOY staff, Kim missed zero. Your reply went yesterday.
  • Seamless, three tranches: 4,524 contacts, 3,648 usable emails, 1,355 domains. Tranche 3 added 127 new people and zero new companies. Two earlier files were BOY's own CRM export, excluded. The 2026 lists aim better but over half their contacts carry no email. The window not yet seen is March through December 2025; that ask is with Nadine. Renewal date and cost are still Brian's estimate, confirm.
  • Stock: Mike 172 waiting, Justin 165, Tom 172, Zintis 171, Brian Network 209, Nick 161. About nine working days for the four rep pools at current pace. Refill is a gated write.
  • This morning's run was clean. 12-item edition sent 06:26 UTC with Cc and Reply-To to you on the first real send, LinkedIn block back after yesterday's one-day platform failure, the "22 voice notes" line gone, CRM sync 16,022 contacts and 9,232 accounts with 0 readback mismatches, 16,806 active contacts rated.

Open items to close on the call

  • Kim's invite timing, and Kim on the reps call.
  • Test-edition picks.
  • The ** and # markers on CRM company names (385 rows / 89 companies; 1,079 rows / 216 companies). If either flags a customer, competitor or dead account it is the fastest exclusion win available.
  • Alaska and Hawaii in nobody's territory. Non-US engaged contacts: 33, mostly Canada and Mexico. Existing customers, agents, distributors and independents in or out of cold audiences.
  • Brian's expenses form and the expenses-lane contact's email (the pack calls her Diana; confirm the name before asking).

Landmines and housekeeping

  • Say "your seat's invitations are landing across your live campaigns at once", not "you're capped" and not how the scheduler works.
  • The hub feed has one stale line (a Tuesday entry still says "proposed for Wednesday at the same 10:30 Eastern slot"). Harmless today, fix after.
  • Two workbook reviews fell off today's edition (address corrections and the no-rating list, both sent 17 Aug); nine LinkedIn blocks filled the cap. Chase by hand on the call.
  • The 101 profiles blacklisted on 19 Aug have not been re-measured; a blacklist entry suppresses future pulls, it does not halt an enrolled target. Do not claim the cull is frozen.
  • REVIEW recheck: the 21 Aug artifact records only Anaforian's row. Safe line: one flagged change came out of the 21 Aug recheck, Anaforian's, and it was actioned. Do not claim full coverage.
  • The Aimfox session token expires Monday 31 Aug at 10:59Z, before the 14:30Z reps rollout call you run live. Renew before the weekend or first thing Monday.
  • No rep-facing edition sender exists. Monday's demo shows a rep edition; do not claim a send path that has not sent.
  • No pricing on any BOY email thread (the IntelliTec consultant is on the canonical build thread and is external to BOY). Marko's private BOS thread stays separate from Brian. 31 Aug is the UK bank holiday, awareness only.

After the call