Customer deployment
Account setup
Answer these at handoff. Every customer gets the same stages, kickoff and weekly sponsor note; the answers change the work involved, not the level of attention.
Health and activation plans
Use at any stage. Check every account weekly. When a sign appears, run an activation plan: find the cause, then get usage back.
Start an activation plan when
Where to look: Plan & Usage (usage by user, app and day, and published-app views), audit logs, or the Admin MCP.
First week of an activation plan
- 1Day 1. Pull usage data: who stopped building, which apps lost users, and when it started.
- 2Days 2–3. Talk to the champion and two or three stalled builders. Ask what got in the way, not whether they like the product.
- 3Day 3. Name the cause: data access, no clear use case, sponsor change, spend limits, blocked publishes, a product gap, or a team change.
- 4Day 4. Pick two quick wins, each with a named owner and a date.
- 5Day 5. Send the sponsor a note with the numbers, the cause and a 30-day plan.
Requests and feedback
Every customer request is logged once with what they asked for, the outcome behind it, how many customers need it, and whether a workaround exists. Then it goes to one of three places.
- 1Works today. The strategist shows them how, and adds it to the training material if others will ask too.
- 2Needs setup or an integration. Goes to the forward deployed engineer's queue, ranked by how much it moves the customer's mutual success plan.
- 3Product gap. Goes to Product with the business case, the customers asking and the revenue involved. No roadmap promises to the customer.
Close the loop: tell the customer where the request went and when they will hear back.
Weekly sponsor note
Sent every week from the first app onward. It reports output and business value, not logins. All names and numbers are made up.
Week 9: 2 more apps live, Finance unblocked, 1 open ask
| Team | In production | New this week | Example |
|---|---|---|---|
| Operations | 4 | +1 | Carrier exception tracker |
| Finance | 2 | +1 | Vendor invoice approvals |
| Customer support | 1 | 0 | Refund lookup |
Counted only when an app has 10 or more end users and 50 or more views.
What it's worth so far
Against the baselines agreed at kickoffBuilders
- 7 building weekly, up from 5
- 6 growing, building at least every other week
- 3 stalled: two are waiting on warehouse data access, one has no use case yet (pairing session booked Thursday)
Governance
- All 7 apps sign in through your SSO, and every query and change is in the audit log
- Code Security caught 2 high-severity findings before publish. Both were fixed with Clark the same day
- 1 Lovable prototype from Ops was imported and now runs on governed integrations instead of a hardcoded database key
Blocked, and what we need from you
- Warehouse data access for two Ops builders. Request is with IT since week 7. Ask: a nudge to the data team lead.
Next week
- Second training group (10 builders, 2 days)
- Demo day with Procurement, who asked to join
Update from a meeting
Paste a transcript or your notes from a customer meeting. Claude reads them against this account's checklists, readiness, health signs, scorecard and brief, and suggests updates, each with the line that supports it. Nothing changes until you apply it.
Transcript or notes
Fictional sample: a made-up SoFi working session. Speakers are labeled by role, and every number is made up.
Open questions
This draft is built from the outside, using public docs. These answers would change it.
- How are deals handed over from Sales today, and what context tends to get lost?
- Which of the templates marked in the checklists already exist, and which would help most to build first?
- What do the current usage dashboards track, and what is missing to tell the value story?
- What is the most common reason customers stall, and does a Hybrid or Cloud-Prem deployment change that?
- How long do Hybrid and Cloud-Prem setups take in practice, and what usually holds them up?
- How is forward deployed engineer time split across accounts, and who decides?
- How many existing customers are still mainly on Low-Code, and is moving them to Clark part of this role?
- How does the team track usage against each customer's commitment, and what pace counts as healthy?
- When does renewal planning start today, and who owns it with the account executive?
- How long does it take today from kickoff to the first app in production, and what usually holds it up?
- Where does account tracking live today, and should these checklists feed into it?
About this draft
A customer deployment playbook drafted by Sardar Ahmar Wasif for a conversation with the Superblocks team, and built with Claude Code.
- What it is. One repeatable process for a new customer, from signed contract to renewal, that adapts to each account's setup and readiness.
- Who it's for. Enterprise accounts, the plan that comes with a dedicated account team, that also fit hands-on deployment: enough spend and company size to justify it, a team that wants hands-on help from post-sales, and leaders willing to push AI adoption internally.
- What it is not. An official Superblocks document or product. The console-style layout is an homage to make it easy to picture in use.
- Data. The SoFi example account uses only SoFi's public information, with sources listed on its overview. Its profile, readiness answers and brief are my assumptions to confirm at handoff, not Superblocks or SoFi data. The SoFi scorecard has no numbers on purpose. The weekly sponsor note is a fictional sample.
- Saved. Account setup, the brief, ticked items, your own watch-outs and the scorecard are saved in this browser only.
- Claude. Update from a meeting sends the pasted text and the account's playbook state to Claude through this site's server, which doesn't store them. Use the sample or your own notes, not confidential customer material.
- Sources. Product details come from the Superblocks docs, the pricing page and How to Prove AI ROI to Your Board, as of October 2026. Thresholds such as the 30% usage drop are my estimates.