Deal Type

Selected workflow updates instantly — toggle between types to compare.
Full Stack (D+C+J+B)
DRIVEN BY MAKE 5490913
17 stages
~25 hr total work
~6 weeks typical elapsed (incl. follow-ups)

First-cut assumptions — needs your review

What's now LIVE in the sequencer (J+B / full-stack default): 6-step P1 chain with 2-day follow-up cadence + "Put on hold" branch · split Send-link/Booking-confirmed stages · P2 Site measure (skip-closeable) · P3 fan-out when P2 closes · sequential P4 + P5.

Still aspirational: per-type variations (Design-only, Cert-only, etc.) — the J+B/full-stack playbook applies for now. Click ✏ Edit Mode below to tweak time estimates and assignees, then export the JSON for me to lock into the per-type playbook.

1

Phase 1 — Engagement

ALL TYPES Showing 
From enquiry to booked meeting · ~1.5 hr work · 1–2 weeks elapsed
  1. SETUP- Acknowledge enquiry, email, name sales task
    ⏱ 15 min 📅 Due in 1d 👤 SBI Workflow Assignee
    Sequencer entry point. Salesperson replies to the inbound enquiry within ~1 business hour, confirms receipt, and renames the parent deal task with the convention TS{YYMMDD} {Surname} — {Project type}. Closing this subtask fires Make scenario 5490913, which auto-creates Project information requested. The first response sets the responsiveness clock for the whole deal.
  2. Project information requested
    ⏱ 15 min 📅 Due in 1d 👤 SBI Workflow Assignee 🔄 Auto-spawned
    Email the client requesting whatever scope detail is missing — plans, photos, brief, site address, intended use, budget range. The salesperson sends and waits. Closing this subtask without the client replying triggers Follow up #1; closing it after the client supplies the info triggers Make Online Meeting Booking.
  3. 3. Follow up #1- Project information (spawned only if no reply within 2d)
    ⏱ 15 min 📅 Due in 1d 👤 SBI Workflow Assignee 🔄 +2d after request
    Auto-cancels if a sibling subtask Project information supplied is closed in the meantime. Otherwise, polite chase email — keep it short, restate what's missing, suggest a 15-min discovery call as an alternative.
  4. 4. Follow up #2- Project information (spawned only if still no reply)
    ⏱ 15 min 📅 Due in 1d 👤 SBI Workflow Assignee 🔄 +2d after #1
    Final chase. Two-way branch:
    • If Project information supplied is closed by then → advance to #5 Send online meeting booking link.
    • If still no reply → 3 days later, sequencer creates the Put on hold task instead. Deal pauses until client re-engages.
  5. ↳ Send "Put on hold" email — better time for client (branch: only if no reply 3d after Follow up #2)
    ⏱ 15 min 📅 Due in 1d 👤 SBI Workflow Assignee 🔄 +3d after #4 (no reply)
    Polite "we'll catch up when timing works for you" email. Closing this pauses the chain — no further automatic stages spawn. Salesperson manually re-engages weeks/months later when client signals readiness.
  6. 5. Send online meeting booking link
    ⏱ 15 min 📅 Due in 1d 👤 SBI Workflow Assignee
    Send Calendly/booking link to the client so they can pick a meeting time. Owned by SBI — close this subtask when the link is sent. The next stage (#6) is then created in a "waiting for client" state.
  7. 6. Online meeting booked
    ⏱ 30 min 📅 Due in 5d 👤 SBI Workflow Assignee
    Waiting-for-client state. Close this subtask when the client actually books a slot (you see the booking confirmation come through). The 30 min time estimate covers the meeting itself plus any pre-meeting prep. Closing fires Phase 2 (Site measure).
2

Phase 2 — Discovery & Scoping

CONDITIONAL Showing 
Site visit only if needed · 2 hr work · up to 4 days elapsed
  1. Site measure (skip-close if not needed)
    ⏱ 2 hr 📅 Due in 4d 👷 Field team / SBI Workflow Assignee
    Conditional stage — site measure is needed only when project information from #2 didn't have enough detail. Site visits are deliberately delayed until after the online meeting (where client gives preliminary approval) — going onsite before the client has signaled commitment risks wasted time + cost if the deal doesn't proceed.

    If you don't need a site visit for this deal (info was sufficient from the meeting), close this subtask immediately — the chain advances to Phase 3 fan-out either way. The 4-day due date is a soft deadline for when the visit should happen if you do need one.
3

Phase 3 — Pricing

FAN-OUT Showing 
All 4 stages spawn at once when P2 closes · 3–14 hr work · 5 days elapsed
  1. Plans for Quoting (Rayon)
    ⏱ 4 hr 📅 Due in 5d 📐 CAD team
    Rayon is SBI's 2D drawing program. Always required for Build deals — every build needs a Rayon plan before Buildsoft can estimate. Architectural plans (whether SBI-produced via the design team or client-supplied) feed in here as inputs; Rayon translates them into the build drawing set used for pricing and site. Closing this stage is one of the two gates that fire Buildsoft Pricing.
  2. Skp for Quoting
    ⏱ 3 hr 📅 Due in 5d 🪚 Joinery team
    SketchUp model of the joinery — cabinet boxes, doors, hardware, finishes. Drives Mozaik pricing and becomes part of the client presentation. Sibling gate with Plans for Quoting — both must close before the consolidated pricing step fires.
  3. Mozaik — Joinery Plans + Pricing
    ⏱ 3 hr 📅 Due in 3d 🪚 Factory / CAD
    Mozaik does the joinery plans (shop drawings — sections, elevations, hardware schedules) and the CNC file processing for manufacturing. SketchUp output from the previous stage feeds in for the visual model; Mozaik produces the production-grade joinery plans, the cut list/materials/hardware, the price, and the CNC files. Note for sequencer rev: the current playbook stage name "Price up Build, Joinery in Mozaik" understates the scope — Mozaik is a plans tool too, not just pricing.
  4. Buildsoft Pricing
    ⏱ 4 hr 📅 Due in 5d 💰 Estimator
    Buildsoft estimate from approved plans — labour, materials, subbie quotes, contingency. Output exported to Excel into 1.2 COST SHEETS/ for the proposal. Sub-quotes from the Contractors & Suppliers list are gathered here via the SBI-RFQ-Contractors-Suppliers skill.
4

Phase 4 — Presentation

ALL TYPES Showing 
Qwilr proposal + the live presentation · 3 hr work · 1 week elapsed
  1. Online Presentation Ready (Qwilr / Plans / Skp)
    ⏱ 2 hr 📅 Due in 3d 👤 SBI Workflow Assignee
    Assemble the Qwilr proposal page — headline, value props, plans/Skp embeds, fixed price, terms. Triggered via the qwilr-proposals skill which generates the HTML structure. Closing this signals "ready to present" — typically followed by booking the presentation slot.
  2. Online Presentation- Done
    ⏱ 1 hr 📅 Due in 7d 👤 SBI Workflow Assignee
    The actual Qwilr walkthrough call — present, answer questions, take feedback. Closing this kicks the deal into the closing-follow-ups stream. Update the parent deal status to PRESENTATION SENT at this point.
5

Phase 5 — Closing Follow-ups

ALL TYPES Showing 
Five-step nudge sequence · ~1 hr work · 5 weeks elapsed
  1. Follow-up #1
    ⏱ 15 min 📅 Due in 1d 👤 SBI Workflow Assignee 🔄 +2d after presentation
    Permissive stream — sequencer can skip ahead or hold off if it sees recent client activity. The aim is steady contact without pestering.
  2. Follow-up #2
    ⏱ 15 min 📅 Due in 1d 👤 SBI Workflow Assignee 🔄 +4d after #1
    Different angle from #1 — lead with new info or social proof (recent similar project, photo).
  3. Follow-up #3
    ⏱ 15 min 📅 Due in 1d 👤 SBI Workflow Assignee 🔄 +7d after #2
    Mid-cycle — try to surface objections directly. "What's holding you back from saying yes?" type message.
  4. Follow-up #4
    ⏱ 15 min 📅 Due in 1d 👤 SBI Workflow Assignee 🔄 +10d after #3
    Last serious nudge before the closing email. Often the most effective — clients have had time to compare, may now be ready to commit.
  5. Follow-up #5 Send Closing email
    ⏱ 15 min 📅 Due in 1d 👤 SBI Workflow Assignee 🔄 +14d after #4
    "Closing the loop — let me know if circumstances change" — politely puts the deal to bed without burning the relationship. Closing this subtask ends the chain (sequencer rule: Follow-up #5 → do_nothing).

Badge Legend

⏱ Time — work hours typically required to complete
📅 Due — days after subtask creation when it's due
👤 SBI Workflow Assignee — read from the parent deal's 🤝 SBI Workflow Assignee custom field (default for all subtasks unless overridden)
👷/🎨/🪚 Specialist — overrides the default for stages that route to a specific team (CAD, Factory, Estimator, Cert specialist)
🔄 Delay — sequencer waits this long before spawning

Export your edits

Copy this JSON and paste it back to me. Each entry has the original stage name as _originalName so I can map your changes back to the Make playbook, the ClickUp template, and the skill docs.

{}
SBI Sales Task Sequencer — workflow visualization v1.0
Driven by Make scenario 5490913 · ClickUp automation #36
First-cut assumptions awaiting Michael's review · 2026-04-29