Choose the lane
The buyer starts from the free review, a service line, a recommendation path, or a specific offer. The chosen item becomes the call focus, not a rigid order.
Operating procedure
Standard procedure for a prepared consulting call.
The goal is simple: turn a buyer's interest into a booked working session with enough context for Jalil to give practical technical direction.
Booking flow
From selected focus to prepared call.
The catalog is used as a shared language. Checkout turns that language into a time, a brief, and an operating record.
Pick a slot
Checkout shows the next three recommended openings first, with an option to expand availability. The selected time becomes a D1 slot lock.
Send context
The buyer adds a work email and a short brief naming the decision, current stack, constraints, and what would make the call useful.
Confirm and prepare
The system saves the booking, creates a calendar hold, sends email, and gives Jalil a structured brief for preparation.
Email procedure
Every request should notify the owner and confirm the buyer.
In production, Cloudflare Email Service sends owner and buyer messages. In simulated mode, the request still saves and records the intended delivery.
New booking alert
Sent to the configured owner inbox with buyer email, preferred time, company lane, selected agenda, context, booking ID, confirmation link, and calendar hold.
Request received
Sent to the buyer with the requested time, selected focus, calendar hold, and confirmation link. The first form should not request private credentials or customer data.
Manual review
If email delivery fails, the booking remains saved in D1 and admin shows the email status so Jalil can follow up manually.
Initial questionnaire
The first brief should answer the useful questions.
A polished deck is not required. The buyer should provide enough truth about the decision, system, constraints, and desired outcome.
Ask in the checkout brief
- What business decision do you need to make after the call?
- What product, workflow, repo, or system brought you here?
- What is the current stack?
- What AI, agent, Cloudflare, React, TypeScript, or open-source work is already in motion?
- What have you already tried?
- What is the biggest constraint: time, budget, data, capacity, risk, or customer pressure?
- What would make the call a win?
- Is there timeline or launch pressure?
Requirements
Keep the first step useful and low-risk.
Required
- Work email
- Company lane
- Preferred call slot
- Short context brief
- Selected focus area or free review starting point
Recommended
- Current stack
- Business pressure
- Team size
- Product or workflow owner
- Public links if useful
Not in first brief
- Passwords
- API keys
- Production credentials
- Customer data
- Private repo access
Preparation and follow-up
The operational to-do list before and after the call.
Preparation checklist
- Review booking context and selected focus.
- Classify the lead: free review, paid strategy candidate, needs clarification, or not a fit.
- Prepare 3-5 clarifying questions.
- Identify the likely decision type.
- Open public links supplied by the buyer.
- Avoid asking for sensitive access until scope is clear.
Follow-up checklist
- Send summary within 1 business day.
- Restate the decision reached.
- List the next three actions.
- Document risks and assumptions.
- Recommend paid workshop, build assist, advisory rhythm, or no next step.
Weekly operations
- Review recent bookings.
- Check failed email delivery.
- Confirm availability is accurate.
- Adjust CTA and catalog copy if lead quality changes.