CoachCal: Executive & Life Coach Session Hub

Problem and target customer

Why this exists

Customer problem

Independent coaches lose hours each week to email back-and-forth for scheduling, package tracking, and goal updates, and have no shared place where clients can see session history, remaining credits, or progress between meetings.

Who pays

Solo executive and life coaches running their own practice who bill through session packages and need a professional client portal without building custom software.

Business model

Monthly subscription for coaches, with a small per-booking transaction fee on paid sessions.

Editorial note

CoachCal connects coach availability, package credits, client booking, private notes, and milestone updates into one reviewable session loop. The first release keeps payment and video calls outside the core so the coaching relationship remains visible and easy to test.

CoachCal: Executive & Life Coach Session Hub addresses a specific operating gap: For operators managing appointments, availability, and service intake, the product provides one reviewable place to move appointments, availability, and intake details from configure coachcal availability to run the operator schedule without losing ownership, evidence, or failure state. Start with the smallest record, owner, evidence, and outcome loop; integrations should support that loop rather than become a second source of truth.

CoachCal: Executive & Life Coach Session Hub uses bookings / month as its operating unit. Variable cost is mainly driven by transactional email, payment processor; keep those charges separate from the infrastructure baseline.

For CoachCal: Executive & Life Coach Session Hub, Run a small set of real appointments, availability, and intake details through the complete flow and measure whether the target operator reaches run the operator schedule without the current manual handoff. This gives the team a concrete way to judge whether the workflow earns a broader feature set.

Choose your next step

What do you need next?

Evaluate the operating tradeoffs quickly, or inspect how to build the MVP.

Evaluate this ideaSee the cost and deployment preview

Compare the three operating paths at the default workload before opening the full calculator.

See cost preview Build this ideaInspect the build blueprint

Review MVP scope, workflow, states, data rules, architecture, and acceptance criteria.

Open blueprint

Evaluation preview

What would it take to run?

Directional infrastructure estimates for the current 500 bookings assumption. Open the full calculator when you are ready to change it.

Open full cost and deployment

ManagedSelected

$25-$85/ month

Managed app hosting, database, backups, and basic observability for the booking workflow.

Lowest operating effort

Lean self-hosted

$8-$48/ month

One small VPS running the app, database, media volume, and backup job.

Lowest baseline cost

More control

$45-$145/ month

Separate app, data, storage, and worker capacity for cleaner operations.

Most separation and control

Build blueprint

Build the first paid use case

Product goal

Who it serves and what it must change

Target user: Operators managing appointments, availability, and service intake
Problem: For operators managing appointments, availability, and service intake, the product provides one reviewable place to move appointments, availability, and intake details from configure coachcal availability to run the operator schedule without losing ownership, evidence, or failure state.
Measurable outcome: A coach can publish availability, allocate package credits, confirm a client session, and see the related milestone update without editing records manually.

MVP scope

What ships now and what waits

Included

Configure coachcal availability intake
Collect service-specific intake with persisted state
Confirm a valid slot review surface
Run the operator schedule and history
Failure, retry, and ownership states
A client-facing scheduling and progress portal built specifically
Scheduling

Excluded

A full marketplace of providers
Dynamic pricing across every service
Native app for every participant
Complex revenue settlement

UX and user flow

Screens, actions, and states

Configure coachcal availability

Apply provider, room, buffer, and blackout rules before exposing a bookable slot.

capture appointments, availability, and intake detailssave evidencesubmit for review

Collect service-specific intake

Store the client's package balance, booking details, and intake answers so the coach can verify the session before it is confirmed.

inspect collect service-specific intake dataretry the stepchange the workflow state

Confirm a valid slot

Expose the decision, owner, and failure state before allowing the workflow to continue.

compare the confirm a valid slot resultedit the decisionaccept or reject

Run the operator schedule

Record the outcome, preserve the history, and make the next action explicit.

record the run the operator schedule outcomenotify the next ownerclose or retry

Primary flow

Apply provider, room, buffer, and blackout rules before exposing a bookable slot.
Store the client's package balance, booking details, and intake answers so the coach can verify the session before it is confirmed.
Expose the decision, owner, and failure state before allowing the workflow to continue.
Record the outcome, preserve the history, and make the next action explicit.

Loading, empty, and error states

Draft
Slot held
Confirmed
Rescheduled
Completed
Cancelled

Core entity outline

Entities and business rules

Service

Stores the service data needed to move appointments, availability, and intake details through the MVP states.

Fields: id, status, created_at, updated_at, owner_id, metadata
Relations: belongs to the booking workflow, has a status transition history

AvailabilityRule

Stores the availabilityrule data needed to move appointments, availability, and intake details through the MVP states.

Fields: id, status, created_at, updated_at, owner_id, metadata
Relations: belongs to the booking workflow, has a status transition history

Appointment

Stores the appointment data needed to move appointments, availability, and intake details through the MVP states.

Fields: id, status, created_at, updated_at, starts_at, ends_at, provider_id
Relations: belongs to the booking workflow, has a status transition history

IntakeResponse

Stores the intakeresponse data needed to move appointments, availability, and intake details through the MVP states.

Fields: id, status, created_at, updated_at, owner_id, metadata
Relations: belongs to the booking workflow, has a status transition history

Coaches

Stores the coaches data needed to move appointments, availability, and intake details through the MVP states.

Fields: id, status, created_at, updated_at, owner_id, metadata
Relations: belongs to the booking workflow, has a status transition history

Clients

Stores the clients data needed to move appointments, availability, and intake details through the MVP states.

Fields: id, status, created_at, updated_at, owner_id, metadata
Relations: belongs to the booking workflow, has a status transition history

Sessions

Stores the sessions data needed to move appointments, availability, and intake details through the MVP states.

Fields: id, status, created_at, updated_at, starts_at, ends_at, provider_id
Relations: belongs to the booking workflow, has a status transition history

Business rules

A appointments, availability, and intake details record needs the fields required for configure coachcal availability before it enters active work.
Every active record has an owner or an explicit queue state before confirm a valid slot.
The outcome from run the operator schedule remains linked to the original record and its history.
A confirmed appointment must recheck availability and retain the rule that produced the slot.

Architecture and data flow