Skip to onboarding
AI ACROBATICSStart today
Forno Street Pizza Co. / onboarding

A clear path
from today to kickoff.

John, start with the scope, the right owners and the approved inputs. We validate the actual setup, confirm the schedule and prove the journey before a small pilot.

Confirm direction today View the Whimsical plan

Part of your existing AI Acrobatics proposal. Delivery begins after the agreement / agreed deposit and required inputs are ready.

01 / agree the boundaries

Settle the decisions that start delivery.

John and Julian confirm these in the final SOW. The email below records direction for that conversation.

Core versus extra website

Confirm the GHL-centered engagement system, operations and Ad 1 engagement roles. The investor website is additional scope with its own price and deliverables to agree. Optional personal use is separately scoped.

Support, term & acceptance

Choose the support level and commitment using the proposal references. Agree included work, providers / usage costs, change control, support boundaries and objective acceptance criteria.

SOW & deposit terms

Confirm exact amount / currency, invoice recipient, deposit and payment milestones. Finalize the agreement and satisfy its agreed deposit requirement before kickoff.

The approximately 15,000 core-build discussion is a reference; currency, exact amount and deposit are unconfirmed. The additional website price is TBD. October 14 is a conditional planning target, and the schedule is confirmed after readiness validation.

02 / people & preparation

Every input has an owner.

Proposed responsibilities below. John confirms the named technical and sales contacts so questions and missing items reach the right person.

Business & offer approval

John Humphrey

Confirm scope and commercial direction. Approve the current offer, legal wording, brand and content. Nominate the technical and sales owners.

Ready when

One dated, approved offer pack and written scope decisions.

Nominated by John

Technical owner

Coordinate the correct GHL account / location, Meta form, phone provider and calendar. Arrange scoped invitations and resolve access gaps.

Ready when

Account and location inventory, working access, approved form and calendar mapping.

Nominated by John

Sales / routing owner

Define closer coverage, lead assignment, business hours, routing, consent and human takeover. Review the lead-to-booking demo with John.

Ready when

Approved routing rules, exception owner and demo acceptance.

Delivery & validation

Julian / AI Acrobatics

Translate the agreed scope into the SOW, validate inputs and native GHL fit, build the agreed workflows and show the test evidence.

Ready when

Readiness check, confirmed schedule, demo results and pilot review.

01 / John / business owner

Approved offer & answers

  • Current offer and legal / compliance-approved language, with source date and approval owner.
  • Approved FAQs, eligibility boundaries and the questions that must go to a human.
  • Reconcile conflicting historical brand, entry minimum, location and date references before use.

Readiness check: John approves one current source pack for the website and assistant.

02 / John / content owner

Brand, video & website

  • Approved logo, brand assets, usage rights and investor website page scope if selected.
  • Confirm the intended 12:08 Vimeo presentation (1185193132), approved supporting content and any edits.
  • Approved website copy, contact destinations and the protected Avestor handoff.

Readiness check: Approved content and website inclusions are recorded; additional work is separately scoped.

03 / Technical owner

Accounts, forms & calendar

  • Correct GHL account / location and the owner who can issue scoped invitations.
  • Actual Meta account and Instant Form, fields, mapping, source tags and completion / call CTA.
  • Phone number / provider, caller identity, calendar / closer, timezone, availability and booking rules.

Readiness check: Julian validates access and one representative lead / booking path against the actual setup.

04 / Sales owner + technical owner

Routing, consent & people

  • Closer assignment, coverage hours, response ownership and escalation contact.
  • Approved assistant introduction, contact permissions, consent language, DND / opt-out and suppression rules.
  • Human takeover / pause rules, exception handling and the people who accept the demo and pilot.

Readiness check: One sender owner per lead / channel and an approved human handoff are testable.

Use scoped account invitations and an agreed private handoff for materials. This public checklist and email draft are for owners, decisions and public links. Do not include passwords, API keys, payment-card data or private investor records.

03 / the shared visual plan

One onboarding map.
Clear gates between stages.

The original Whimsical board connects today’s decisions and inputs to validation, demo acceptance, a small pilot and rollout.

Forno / onboarding, owners & launch gatesOpen Whimsical board
Whimsical onboarding flow: scope and owners; approved content, accounts and routing; agreement and deposit readiness gate; proposed days one to two validation; confirmed schedule; lead-to-booking demo; acceptance; small pilot; rollout. Missing inputs and revisions loop back to their owner.
Explore the embedded Whimsical board

Preview exported from the genuine Whimsical board. Open the board for full-size viewing; the input checklist and phase gates are also written out on this page.

04 / proposed sequence

The schedule follows readiness.

Proposed days 1–2 start after the prerequisites are complete. Build and pilot dates depend on the selected scope, access and review turnaround.

  1. 01
    Today · decisions & inputs

    Confirm direction together

    John and Julian agree core scope versus the extra investor website, support / commitment, SOW boundaries and deposit terms. John nominates owners; the team gathers the approved inputs.

    Exit gate

    Signed agreement, agreed deposit requirement satisfied and required inputs ready. Missing items get a named owner; timing stays provisional.

  2. 02
    Proposed days 1–2 · after readiness

    Validate before scheduling

    Julian checks the actual GHL / Meta / phone / calendar access, current offer, mapping, consent and native GHL fit with the technical and sales owners.

    Exit gate

    Readiness findings resolved and a scope-specific build / demo schedule confirmed together. Unresolved dependencies return to their owner.

  3. 03
    Confirmed schedule · build & demo

    Prove the connected journey

    Build the agreed flow and demonstrate a controlled test lead through engagement, booking, GHL readback and a useful closer brief. Show opt-out, duplicate, failed-delivery and takeover behavior.

    Exit gate

    John and the sales owner review the evidence against SOW acceptance criteria. Defects are corrected; extra scope requires a written decision.

  4. 04
    After acceptance · small pilot

    Learn, then expand

    Run a small, approved cohort with named human coverage. Review delivery, consent, bookings, attendance, routing and exceptions before increasing the rollout.

    Exit gate

    Review pilot evidence together and authorize broader rollout. Pause or correct the affected flow if the agreed checks fail.

05 / start today

Send the direction.
We’ll confirm the details.

Choose the direction and add owners if you have them. Open the email draft, review it and send it to Julian to coordinate the final SOW and readiness check.

Open onboarding email draft

Opens a draft to julian@aiacrobatics.com in your email app. Review it and send it yourself. These choices are not submitted or saved by this page; opening the draft does not sign an agreement or start delivery.