Pemba Capital PartnersCEO Day Guide

Vercel × Pemba · CEO Day · 19 November

You've been seconded as CEO.

Switchback Systems needs you for the afternoon. Customers slip away, nobody trusts the pipeline, and tenders get answered blind. Pick a problem and build the agent that fixes it, in plain English, with v0.

  • 90 minutes
  • 3 problems, or your own
  • Live in minutes

Start here

Four steps

  1. Your laptop is ready

    v0 is open on your table's project. A sign-in page instead? Wave a facilitator over.

  2. Pick roles

    The Driver types. The Navigator follows this guide. The Checker tries the app and checks the numbers.

  3. Fix your problem

    Your table card names your problem, below. Tell v0 what you want in your own words, and Publish after each change. Stuck? Open the prompts under your problem.

    See the problems

    Your live app: ceo-day-table-<number>.vercel.app. Stuck? See Help.

  4. Paste Kickoff

    Kickoff builds the app, puts the chat on the right and connects your data. v0 takes a minute or two. Then click Publish.

    Kickoff
    Build the app shell for a laptop screen:
    - A navy header with the Pemba logo (https://pemba-ceo-day-guide.vercel.app/brand/pemba-logo.png, at least 48px high).
    - An empty main area for what we build next.
    - A chat panel docked on the right, open by default, where we ask questions about our data. Use the AI SDK through AI Gateway with the model in MODEL_ID, and show each answer's cost under it.
    
    Our data is already connected to this Vercel project through Vercel Connect, so no API keys go in the code. On the server, get a token with getToken(process.env.<connector>, { subject: { type: "app" } }) from @vercel/connect:
    - HubSpot CRM (HUBSPOT_CONNECTOR): our US customers, contacts, deals, products and tickets, through the HubSpot CRM API. Any change to a record must wait for us to click Approve in the chat.
    - Xero (XERO_CONNECTOR): our invoices to those customers, in AUD, through the Xero Accounting API. Read only; skip voided invoices. Each invoice's Contact.ContactNumber matches the x_seed_id property on its HubSpot company. Xero allows 60 requests a minute, shared by every table: read the invoices once and keep them for five minutes.
    - Company websites (FIRECRAWL_CONNECTOR): a company's public pages, through Firecrawl.
    - Web search: AI Gateway's web search tool, at most three searches an answer.
    - Tender room: eleven tenders and our own documents, as one JSON list (path, title, kind, owner, updated, expires, text) in this project's private Blob store. Read it with get("tender-room/index.json", { access: "private" }) from @vercel/blob.
    
    Then tell me, one line each, what we can use from HubSpot CRM, Xero, Firecrawl and web search, and the tender room.

Your new company

Switchback Systems

You've just been seconded to run Switchback. It sells software that runs inspections, permits and incidents across many sites, to large US companies.

Your app starts blank. Its Vercel project is already connected to Switchback's US book in HubSpot (real companies, USD), its invoices in Xero (AUD), company websites, web search and the tender room. Kickoff wires them in. What's connected

Product A

Switchback Sites

The core platform. Every customer has it.

  • Inspections and checklists in any browser
  • Permits to work and contractor sign-in
  • Incidents, near misses and corrective actions
US
US$240,000 a year
Buyer
VP Operations, Head of EHS

Product B

Switchback Insights

Analytics on top of Sites.

  • Compliance by site and region
  • Monthly board packs
  • Overdue actions and risk trends
US
US$90,000 a year
Buyer
Director of EHS, finance

Product C

Switchback Connect

Plugs Switchback into the systems around it.

  • HR sync for staff and contractor credentials
  • ERP and maintenance work orders
  • Sensor alerts that open incidents
US
US$60,000 a year
Buyer
IT applications

Product D

Switchback Assure

Switchback's team runs compliance for you.

  • Audit evidence prepared
  • Monthly regulatory reporting
  • Support through regulator visits
US
US$180,000 a year
Buyer
Head of EHS

Product E

Switchback Academy

Gets site teams using it.

  • Onboarding for site managers
  • Refreshers, in more than one language
  • Train-the-trainer
US
US$30,000 once
Buyer
Training lead

Product F

Premium Success

Faster help, a named person.

  • 1-hour response on priority-one incidents
  • A named customer success manager
  • Quarterly business reviews
US
US$45,000 a year
Buyer
Operations lead

The problems

Three problems on your desk, or your own

All five sources are available for every problem: HubSpot, Xero, company websites, web search and the tender room.

Reason to Call

Customers slip away before anyone calls.

Renewals come round with nobody having spoken to the customer in months. Unhappy accounts go unnoticed, urgent tickets sit open, and some customers owe us money. The facts are spread across HubSpot, Xero and the customers' own websites, so nobody sees the whole picture.

Your job: Give the sales team a ranked list of who to call this week, why, and what to say.

  1. Base camp. Who to call, and why.
  2. Summit. A draft for each call.
  3. Stretch. Check their website first.
Need a hand? Show the promptsBase camp, Summit, Stretch
  1. Base camp prompt
    In the main area, show the customers we should call this week, and why: renewing soon, gone quiet, unhappy, or an urgent ticket. Most reasons first, with the records behind each.
  2. Summit prompt
    Okay, now add a Draft button to each one: a line on why to call now, and a message to our champion there under 80 words, with the records it relies on listed underneath. Approve or Skip; nothing sends.
  3. Stretch prompt
    Before we call, check their website: is our CEO still right, and what have they announced lately?

Read the Terrain

Nobody trusts the pipeline.

The board asks how much is in the pipeline and what's stuck, and every answer comes with a caveat. Deals are entered twice, have no amount or no owner, and sit past their close dates. Before anyone can plan, someone has to show what's real and what isn't.

Your job: Give the board pipeline numbers it can trust, and flag the records that need fixing.

  1. Base camp. Four numbers, and the deals behind them.
  2. Summit. Bad data, counted and flagged.
  3. Stretch. Answers to pipeline questions.
Need a hand? Show the promptsBase camp, Summit, Stretch
  1. Base camp prompt
    Turn the main area into a pipeline dashboard: open pipeline, stuck deals, deals past their close date and win rate on top, and the open deals in a table below.
  2. Summit prompt
    Now add a "Can we trust this?" panel: duplicate companies, duplicate contacts, deals with no amount, deals with no owner, and contacts with no company. A count and five examples for each.
  3. Stretch prompt
    Add an Ask box with three buttons: which deals are at risk this quarter, where the pipeline is stuck, and what to fix in the CRM first. Answers cite deal IDs.

Bid or Walk

We answer tenders blind.

Eleven requests for tender are sitting in the tender room. Some we would win, some ask for things we can't deliver, and some aren't for us at all. The evidence is spread across our own certificates, policies and past proposals, and some of it has expired. Each response takes days, so we need to know which ones are worth it.

Your job: Decide bid or walk on every tender, with evidence from our own documents.

  1. Base camp. Each tender and what it asks for.
  2. Summit. Each requirement judged against our documents.
  3. Stretch. The call, every reason cited.
Need a hand? Show the promptsBase camp, Summit, Stretch
  1. Base camp prompt
    In the main area, show the tenders with their buyer and closing date, soonest first. Click one to see what it asks for, mandatory first.
  2. Summit prompt
    Now find our evidence for each requirement, and with one AI call for the whole tender judge each one: met, partly met or not met, quoting the line. Flag every mandatory requirement we don't fully meet.
  3. Stretch prompt
    Give me the call: bid, bid with conditions, or walk, with the reasons and gaps, each citing a document.

Your Own Route

Bring a problem we haven't listed.

Every company has one: the report that takes a day to pull together, the question nobody can answer quickly, the customers who fall through the gap between two systems. Pick one Switchback has, or one your own business has, and solve it with Switchback's data.

Your job: Name the problem and who it's for, then build the agent that fixes it.

  1. Base camp. The problem, and the data behind it.
  2. Summit. What to do about it, with the evidence.
  3. Stretch. Ready to use on Monday.
Need a hand? Show the promptsBase camp, Summit, Stretch
  1. Base camp prompt
    Our problem: [one sentence: what goes wrong, and who it hurts]. In the main area, show the records that matter for it, from whichever of HubSpot, Xero, the tender room, company websites and web search it needs. Work the numbers out in code and show the records behind each one.
  2. Summit prompt
    Okay, now have the agent say what we should do about each one, citing the records it relies on. If it should change a HubSpot record, show the change with Approve and Deny first.
  3. Stretch prompt
    Make it something we'd use on Monday: [who would use it] opens it, sees what needs doing first, and acts on it. Show what it would save us each week.