Home/How it works/Sample plans/Saltmarsh Charters
Sample plan · fictional company

Saltmarsh ChartersCharter booking marketplace: a sample sprint plan

A two-founder startup builds one place to book local fishing and boat charter captains, with deposits, weather rules and payouts built in.

  • TypeStartup, first version
  • IndustryFishing and boat charters
  • Size2 founders, 12 charter captains signed up for launch on one stretch of coast
  • Plan5 monthly sprints, 29 cards

Saltmarsh Charters and everyone in this plan are made up. The format is real: it is how I plan and run every web app build, one board per month, reviewed with the client every Thursday.

The brief

The problem today

Charter captains on the Carrow Sound coast take bookings by phone, text and Facebook messages, often from the boat with one hand on the wheel. Customers can't see who is free on a given day, deposits are sent by app transfer or not at all, and when the wind picks up, every rescheduled trip is a string of calls. Visitors give up and book somewhere else, and captains lose days they could have filled.

What the app has to do

A marketplace where a visitor can find a captain, see real availability, book and pay a deposit in a few minutes, and get moved to a new date automatically when the marine forecast says the trip is off. Captains get paid out directly and see every trip in one dashboard; the founders approve captains and settle disputes from one admin screen.

Who uses it

Founder admin
Nora Pike and Sam Okoye, the two founders

Approve new captains after a license and insurance check, watch bookings and fees, and settle disputes.

Captain
Independent charter captains, each with one or two boats

Set their trips and availability once, get booked without phone tag, and get paid out without chasing deposits.

Customer
Visitors and locals booking a trip, often a family or a group of friends

Compare captains, see open dates, book and pay a deposit on a phone, and know quickly if weather moves the trip.

What gets built

Browse and search The public side of the marketplace, where visitors find a trip by date, trip type and group size. 2 screens
Home and search

The first screen a visitor sees, with a search bar and featured trips.

  • Search bar with date picker, trip type (inshore, offshore, sunset cruise) and number of guests
  • Featured trips row with photo, captain name, length and starting price per trip
  • Departure harbor filter (Port Ellery, Wren Inlet, Cutter's Landing)
  • How it works strip, book, pay a deposit, weather-safe rescheduling
Search results

Trips that fit the date and group size, sorted by rating or soonest open slot.

  • Trip cards with boat photo, captain, rating, trip length and guests allowed
  • Open on your date badge or next open date
  • Sort by rating, price or trip length
  • Map toggle showing departure harbors
Captain profiles Each captain's page, with their boats, trip types, photos, bio and reviews, so a visitor can pick a person, not just a boat. 2 screens
Captain profile

Who the captain is, what they run and what past guests said.

  • Bio, years on the water and license type
  • Verified badge once the founders approve license and insurance
  • Boats with photos, length, guest limit and amenities
  • Trip list with length, what's included and price per trip
  • Reviews with star rating, trip type and month of the trip
Trip detail

One trip on one boat, with a calendar of open dates and the book button.

  • Photo gallery
  • What to bring, what's included, departure point and parking notes
  • Availability calendar with open, few left and full days
  • Cancellation and weather policy summary
  • Book this trip button
Booking and payments Online booking with a deposit through Stripe Connect, so the captain is paid directly and the platform keeps its booking fee. 2 screens
Checkout

Pick a date and time slot, enter guests and contact details, pay the deposit.

  • Date and time slot picker (morning half day, afternoon half day, full day, sunset)
  • Guest count with the boat's limit enforced
  • Deposit, booking fee and balance due on the day, shown as percentages of the trip price
  • Card payment with Stripe
  • Agree to cancellation policy and terms checkbox
Booking confirmation

What the customer sees after paying, also sent by email and text.

  • Trip, date, departure harbor and meeting time
  • Captain name and phone, shown only after booking
  • Add to calendar link
  • Change or cancel button with the policy in plain words
Weather and rescheduling A daily check of the National Weather Service marine forecast for each harbor that flags risky trips and starts the reschedule flow. 2 screens
Weather watch

The captain's and founders' view of upcoming trips with the forecast against each one.

  • Trips in the next 72 hours with wind, wave height and any Small Craft Advisory
  • Green, watch and likely cancel status per trip
  • Captain's call button, go or cancel for weather
  • Last forecast update time
Reschedule

The customer's page to pick a new date or take a refund after a weather cancellation.

  • Why the trip was called off, with the forecast that triggered it
  • Next open dates on the same trip and boat
  • Move my trip button, deposit carries over
  • Refund my deposit button
Captain dashboard Everything a captain needs between trips, on a phone, trips, availability, payouts and customer contact. 3 screens
My trips

Upcoming and past trips, with guest details and status.

  • Today and next 7 days list with time, trip, guests and deposit status
  • Tap to call or text the customer
  • Mark trip completed or no-show
  • Weather status from weather watch on each trip
Availability

The captain's calendar per boat, where they open, block and adjust days.

  • Month view per boat
  • Block a day or a slot with a reason (maintenance, private, personal)
  • Repeat weekly pattern, for example no trips on Mondays
  • Season start and end dates
Payouts

What has been paid out, what is pending, and the fee on each booking.

  • Payout list with date, trips covered and status from Stripe
  • Per booking deposit, booking fee and net to the captain
  • Link to the captain's Stripe Express dashboard
Admin The founders' side, approving captains, watching bookings, and handling disputes and refunds. 3 screens
Captain applications

New captain sign-ups waiting for a license and insurance check.

  • Application list with status (new, documents missing, approved, declined)
  • Uploaded Coast Guard license and insurance certificate with expiry dates
  • Approve or decline with a note to the captain
  • Reminder 30 days before a license or insurance document expires
Disputes

Complaints and refund requests in one queue, with the booking history beside them.

  • Dispute list with reason (no-show, weather, trip cut short, other)
  • Booking timeline with payments, messages and weather calls
  • Refund full, partial or none, with a note to both sides
Overview

The founders' numbers for the launch, on one screen.

  • Bookings this week and since launch
  • Captains live, captains with a booking, captains with none yet
  • Weather cancellations and how many were rescheduled vs refunded
  • Booking fees earned this month

How the main jobs flow

Search to booked trip
  1. A visitor searches for an inshore trip for 4 guests on a Saturday out of Port Ellery.
  2. They open Capt. Ray Delacroix's profile, read the reviews and open the half day inshore trip.
  3. They pick the morning slot, enter guests and pay the deposit plus the booking fee by card.
  4. Stripe Connect sends the deposit, less the booking fee, to Ray's account.
  5. The customer gets an email and a text with the meeting time; Ray gets a text and sees the trip in My trips.
Weather cancellation and reschedule
  1. The morning check pulls the marine forecast for each harbor and flags a Saturday trip as likely cancel, with a Small Craft Advisory and 25 knot gusts.
  2. The captain gets a text the day before and taps cancel for weather.
  3. The customer gets a text and email with a link to the reschedule page.
  4. The customer moves to the next open Sunday, or takes a full deposit refund.
  5. The founders see the cancellation, and what the customer chose, on the overview.
New captain onboarding
  1. A captain applies with their boat details, license and insurance certificate.
  2. A founder checks the documents and approves the application.
  3. The captain connects a Stripe account for payouts and builds their profile, boats and trips.
  4. The captain sets their availability and the profile goes live in search.

How we will know it worked

  • All 12 launch captains approved, connected to Stripe and live with at least one bookable trip by public launch.
  • At least 10 of the 12 captains take a paid booking through the platform in the first 60 days.
  • 150 paid bookings in the first 60 days after public launch.
  • Most weather cancellations rescheduled or refunded by the customer from the link, with no phone call to the founders.
  • No booking paid out to a captain whose license or insurance has expired.

Not in this build

  • A native phone app; the customer and captain screens work in the phone's browser.
  • More than one region. The app is built so new harbors can be added later, but launch is Carrow Sound only.
  • Gift cards, multi-trip packages and promo codes.
  • Fishing license sales and fish cleaning or processing add-ons.
  • Messaging inside the app; captain and customer contact is by phone and text after booking.
Build notes: integrations, data and sample records

Integrations

  • Stripe Connect: Deposits taken at booking and paid out directly to each captain's own account, with the booking fee kept by the platform.
  • National Weather Service API: Marine zone forecasts and Small Craft Advisory alerts for each departure harbor, checked every morning.
  • Twilio: Text messages for booking confirmations, day-before reminders and weather cancellations.
  • Resend: Booking confirmations, receipts, reschedule links and captain application emails.

Data

Captain

name, phone, email, bio, years on water, license number, license expiry, insurance expiry, status, Stripe account, rating

Boat

captain, name, type, length, guest limit, amenities, photos, home harbor

Trip

boat, type (inshore, offshore, sunset cruise), length hours, slots, price, included, what to bring, active

Availability block

boat, date, slot, reason, repeat pattern

Booking

trip, date, slot, customer, guests, deposit percent, booking fee percent, status, weather status, rescheduled from

Customer

name, email, phone, bookings, text opt-in

Payout

captain, Stripe payout id, bookings, gross, fees, net, paid on, status

Review

booking, customer, captain, stars, text, posted on, hidden by admin

Dispute

booking, raised by, reason, notes, outcome, refund amount, closed on

Sample records for the prototype

  • Founders: Nora Pike (operations, admin) and Sam Okoye (captain relations, marketing).
  • Harbors: Port Ellery (main harbor, 7 captains), Wren Inlet (3 captains), Cutter's Landing (2 captains).
  • Capt. Ray Delacroix, Port Ellery: Reel Easy, 24 ft bay boat, 4 guests, half day and full day inshore for redfish and trout, 4.9 stars from 38 reviews.
  • Capt. June Halvorsen, Port Ellery: Second Wind, 36 ft sportfisher, 6 guests, full day offshore for mahi and tuna, 4.8 stars from 21 reviews.
  • Capt. Eli Barrow, Wren Inlet: Low Tide Lady, 26 ft pontoon, 10 guests, 2 hour sunset cruise, and Marsh Hen, 18 ft skiff for inshore.
  • Capt. Tessa Marchetti, Cutter's Landing: Gray Heron, 22 ft center console, 3 guests, fly fishing the flats, new captain awaiting insurance check.
  • Booking: Brennan family, 4 guests, half day inshore with Ray, a Saturday in May, 25% deposit paid, balance due on the dock.
  • Booking: Alex Moreno and three friends, full day offshore with June, flagged likely cancel for a Small Craft Advisory, reschedule link sent.
  • Booking: Priya and Dev Raman, sunset cruise with Eli, completed, 5 star review: Eli knew every bird on the marsh.
  • Dispute: Carter party, offshore trip cut short at 4 hours for a mechanical issue, partial refund requested, open.
  • Payouts: Ray, 6 bookings this week, paid out Tuesday; June, 2 bookings, pending.

The plan, month by month

Each month has its own board. Cards are numbered in the order they are worked across the whole plan. Each card shows what I build and, where it applies, what I need from the client. If something from the client arrives late, the cards after it move back by the same amount.

AIwhirks' part Saltmarsh Charters's part

These are best-case sprints: they assume no delays, no changes to scope and no surprises. Progress is reviewed every Thursday. Months further out are less certain, so each one is planned in detail at the review that ends the month before.

Month 1

First-version scope and a prototype in front of captains

Scope and prototype

We agree with Nora and Sam what goes in version 1 and what waits, show a clickable prototype to real captains and customers before any code, and set up accounts in Saltmarsh Charters' name.

  • First-version scope agreedEnd of week 1
  • Prototype tested with 3-5 captains and customersEnd of week 3
  • Build plan signed offEnd of week 4

A startup's biggest risk is building the wrong thing, so the first month is about deciding and testing, not coding.

Week 1 Thursday check-in
1 Scope and prototype Week 1

Kickoff and first-version scope

A working session with both founders to list everything the marketplace could do, then sort it into version 1, soon after launch, and later. Version 1 is only what a captain and a customer need to complete a paid booking safely.

AIwhirksRun the session, write the version 1 list and the later list, and turn version 1 into the build plan we build and test against.
Saltmarsh Charters · Middle of week 1Three hours with Nora and Sam. Bring: the list of 12 captains signed up, how each takes bookings today, and any questions captains have already asked you.
2 Scope and prototype Week 1

Accounts in Saltmarsh Charters' name

The app, its data and the Stripe platform account belong to the company from day one, not to us.

AIwhirksSend step-by-step setup notes, then set everything up once you invite us. We never need your passwords.
Saltmarsh Charters · End of week 1Create the hosting, email, Twilio and Stripe accounts in Saltmarsh Charters' name, apply for Stripe Connect, and invite Travis to each.
Week 2 Thursday check-in
3 Scope and prototype Weeks 1-2

Clickable prototype first

The main screens from search to booking, a captain's profile and dashboard, and a weather reschedule, filled with sample captains and trips. It looks real but nothing is coded yet, so changing it is cheap.

AIwhirksBuild the prototype from the version 1 list in card 1 and walk both founders through it before anyone else sees it.
Saltmarsh Charters · End of week 2A 45-minute walkthrough with both founders, then one list of changes before we show it to captains.
4 Scope and prototype Weeks 2-3

Founder decisions on fees and policy

The numbers the app has to enforce. Booking fee percent and who pays it, deposit percent, when the balance is due, and the cancellation rules for customers, captains and weather.

AIwhirksSend a one-page decision sheet with common choices in the charter trade, and build whatever you decide into the plan.
Saltmarsh Charters · End of week 3Decide the booking fee, deposit percent and cancellation policy, for example a 25% deposit, full refund 72 hours out or for weather, no refund inside 24 hours.
Week 3 Thursday check-in
5 Scope and prototype Week 3

Test the prototype with captains and customers

Short sessions with 3-5 real people, at least two captains and two people who have booked a charter before. Each one tries to do their main task while we watch and take notes.

AIwhirksRun the sessions on a video call or on the dock, and write up what tripped people up and what they asked for.
Saltmarsh Charters · Start of week 3Line up 2-3 captains and 2 past charter customers for 30 minutes each, for example Ray, June and Eli.
6 Scope and prototype Weeks 3-4

Terms of service and privacy policy

The marketplace needs terms for customers, an agreement for captains and a privacy policy before the first real booking. These come from your lawyer; we make sure the app matches them.

AIwhirksSend your lawyer a short list of what the app does with payments, refunds and personal data, so the documents fit how it works.
Saltmarsh Charters · End of week 4Brief your lawyer this week. Final documents are needed before the beta in Month 4.
Week 4 Thursday: month review
7 Scope and prototype Week 4

Month review and next plan

What the prototype tests changed, the final version 1 build plan for sign-off, and the board for Month 2.

AIwhirksFold the test notes from card 5 and your decisions from card 4 into the plan, and walk through it with you.
Saltmarsh Charters · End of week 4Sign off the build plan, or mark what still needs to change.
Month 2

Captains, boats and trips

Captains and listings

Captains apply, the founders approve them after a license and insurance check, and each captain builds a profile with boats, trips, photos and availability.

  • First captain approvedEnd of week 1
  • Captain profiles and trips live on stagingEnd of week 3
Week 1 Thursday check-in
8 Captains and listings Week 1

Sign-in and roles

Founders, captains and customers each sign in with their own account and see only what their role needs. Customers can also book as a guest with just an email and phone.

AIwhirksBuild sign-in, the three roles and the founders' admin accounts.
Saltmarsh ChartersUses the role list from card 1, nothing new.
9 Captains and listings Weeks 1-2

Captain applications and approval

A captain applies with their boat details, Coast Guard license and insurance certificate. Nora or Sam checks them and approves or declines with a note. Expiry dates are stored so nobody stays live with lapsed papers.

AIwhirksBuild the application form, the admin approval queue and the 30-day expiry reminder.
Saltmarsh Charters · End of week 1Confirm what counts as approved, for example license type and minimum insurance cover, and who on your side checks it.
Week 2 Thursday check-in
10 Captains and listings Weeks 2-3

Captain profiles, boats and trips

Each approved captain gets a profile with a bio, their boats with photos and guest limits, and their trips with length, what's included and price.

AIwhirksBuild the profile, boat and trip screens, and the trip detail page visitors will see.
Saltmarsh Charters · End of week 3Collect from each pilot captain a short bio, 6-10 good boat and trip photos, and their trip list with prices. Sam usually gets this fastest by visiting the dock.
Week 3 Thursday check-in
11 Captains and listings Week 3

Availability calendar per captain and boat

Each boat has its own calendar with time slots. Captains block days for maintenance or private trips, set a weekly pattern and their season dates, and a slot closes the moment it is booked.

AIwhirksBuild the calendar and the slot rules, using the trips from card 10.
Week 4 Thursday: month review
12 Captains and listings Weeks 3-4

Browse and search

The public home page and search, by date, trip type, harbor and group size, showing only trips that are actually open.

AIwhirksBuild search and results, and load the first pilot captains so the founders can try it on staging.
Saltmarsh Charters · Middle of week 4Nora and Sam each search for five trips the way a visitor would and send notes.
13 Scope and prototype Week 4

Month review and next plan

What got done, what moved, and the board for Month 3.

AIwhirksUpdate this plan and walk through it with you.
Month 3

Booking, deposits and payouts

Booking and payments

Customers book and pay a deposit online, Stripe Connect pays each captain directly with the booking fee kept by the platform, and captains get their dashboard.

  • Captains connected to StripeEnd of week 1
  • First test booking paid out end to endEnd of week 4

Stripe Connect needs the platform account verified before captains can connect, which is why it is applied for in Month 1.

Week 1 Thursday check-in
14 Booking and payments Week 1

Captains connect for payouts

Each captain links their own Stripe account from their dashboard in a few minutes. Their bank details stay with Stripe; neither you nor we ever see them.

AIwhirksBuild the Stripe Connect onboarding and the connected or not yet status on the admin screen.
Saltmarsh Charters · End of week 1Ask each pilot captain to connect their Stripe account this week. Sam follows up with anyone stuck.
Week 2 Thursday check-in
15 Booking and payments Weeks 2-3

Checkout with a deposit

Pick a date and slot, enter guests and contact details, agree to the policy, and pay the deposit and booking fee by card. The balance is paid to the captain on the day, as most captains do now.

AIwhirksBuild checkout using the fee and deposit decisions from card 4, with the booking fee taken out before the deposit reaches the captain.
Week 3 Thursday check-in
16 Booking and payments Week 3

Confirmations and reminders

The customer gets an email and a text with the trip, meeting time and the captain's phone. The captain gets a text for every new booking, and both get a reminder the day before.

AIwhirksBuild the messages with Resend and Twilio, and send you every one of them to read.
Saltmarsh Charters · Middle of week 3Read each message and change any wording that doesn't sound like Saltmarsh Charters.
17 Booking and payments Weeks 3-4

Captain dashboard

My trips, availability and payouts on the captain's phone. Tap to call or text a customer, mark a trip completed or no-show, and see the net payout on each booking.

AIwhirksBuild the dashboard and test it on the phones two of your captains actually use.
Week 4 Thursday: month review
18 Booking and payments Week 4

First booking end to end

A founder books a real trip with a pilot captain using a real card, the deposit lands in the captain's account, and the booking fee lands in Saltmarsh Charters' account.

AIwhirksRun it with you, check every email, text and payout, and fix what we find.
Saltmarsh Charters · Middle of week 4Pick one captain, for example Ray, and book one of his trips yourselves.
19 Scope and prototype Week 4

Month review and next plan

What got done, what moved, and the board for Month 4.

AIwhirksUpdate this plan and walk through it with you.
Month 4

Weather, reviews and the beta

Weather and trust

The marine forecast flags risky trips and customers reschedule from a link, reviews and disputes go in, and four captains start taking real bookings in a soft launch.

  • Weather watch liveEnd of week 1
  • Soft launch with 4 captains and real bookingsEnd of week 4
Week 1 Thursday check-in
20 Weather and trust Weeks 1-2

Weather watch from the marine forecast

Every morning the app reads the National Weather Service marine forecast for each harbor and flags trips in the next 72 hours as green, watch or likely cancel. The captain still makes the call.

AIwhirksBuild the forecast check and the weather watch screen, with the wind and wave limits per trip type.
Saltmarsh Charters · Middle of week 1Agree with two or three captains the wind and wave limits for inshore, offshore and sunset trips.
Week 2 Thursday check-in
21 Weather and trust Weeks 2-3

Cancel for weather and reschedule

When a captain calls a trip off, the customer gets a text and email with a link to move to another open date or take a full deposit refund. Customer and captain cancellations follow the policy from card 4.

AIwhirksBuild the cancel, reschedule and refund flow, using the forecast from card 20.
Week 3 Thursday check-in
22 Weather and trust Week 3

Reviews and disputes

After a completed trip the customer is asked for a star rating and a few words. Complaints and refund requests go to one dispute queue for the founders, with the booking history beside them.

AIwhirksBuild reviews, the founders' option to hide a review, and the dispute queue with full, partial or no refund.
Saltmarsh Charters · End of week 3Decide your review rules, for example only after a completed trip, and when you will hide one.
Week 4 Thursday: month review
23 Beta and launch Week 4 into Month 5

Soft launch with four captains

Four pilot captains take real bookings from people they invite, friends, regulars and their Facebook followers. The site is not promoted yet. Terms and the privacy policy from card 6 must be live first.

AIwhirksPut the legal pages live, watch every booking and payout, and fix issues in order of importance.
Saltmarsh Charters · Start of week 4Pick the four beta captains, for example Ray, June, Eli and one from Wren Inlet, and ask each to send their booking link to 10 regulars.
24 Scope and prototype Week 4

Month review and next plan

What got done, what the first beta week showed, and the board for Month 5.

AIwhirksUpdate this plan and walk through it with you.
Month 5

Fixes, public launch and handover

Beta and launch

We fix what the beta turned up, bring the rest of the 12 captains live, open the marketplace to the public, and hand over the system.

  • All 12 captains liveEnd of week 2
  • Public launchStart of week 3
  • Handover completeEnd of week 4
Week 1 Thursday check-in
25 Beta and launch Weeks 1-2

Fix what the beta found

Everything the four captains and their customers hit during the beta, most important first, each fix shown to the captain who found it.

AIwhirksFix, re-test and show each one.
Saltmarsh Charters · Start of week 1Mark each note "must fix before launch" or "can wait".
Week 2 Thursday check-in
26 Beta and launch Weeks 1-2

The other eight captains go live

The remaining captains are approved, connected to Stripe, and have their profiles, trips and availability set up, so search is full on launch day.

AIwhirksRun a short onboarding call for each captain and set up anything they get stuck on.
Saltmarsh Charters · End of week 2Sam books a 30-minute call with each remaining captain and collects their photos and bios ahead of it.
27 Beta and launch Week 2

Founders' launch overview

One screen with bookings this week and since launch, captains live and captains with no booking yet, weather cancellations, and booking fees earned.

AIwhirksBuild the overview and walk Nora and Sam through it.
Week 3 Thursday check-in
28 Beta and launch Week 3

Public launch

The marketplace opens to everyone. Captains switch their phone and Facebook bookings to their profile link, and Saltmarsh Charters starts its launch marketing.

AIwhirksRun the launch checklist, watch every booking for the first week and stay on call.
Saltmarsh Charters · Start of week 3Send launch announcements to captains, harbors and local visitor pages, and ask each captain to pin their profile link on Facebook.
Week 4 Thursday: month review
29 Beta and launch Week 4

Handover and what comes next

The system documents, a backup check, a guide for each role, and the later list from card 1 sorted by what the launch showed. Optional monthly support from here is your choice.

AIwhirksHand over the documents, run a restore test with you, and present the next-features list.
Saltmarsh Charters · End of week 4Decide whether you want monthly support after launch.

Saltmarsh Charters · Charter booking marketplace · Best-case schedule: assumes no delays, changes or issues.

Questions about this plan

How long does it take to build a charter booking marketplace?

This sample plan takes 5 monthly sprints, from kickoff to handover. The big milestones are prototype tested with 3-5 captains and customers (Month 1), first test booking paid out end to end (Month 3), soft launch with 4 captains and real bookings (Month 4) and public launch (Month 5). A real build's length depends on its scope, and the plan is reviewed every Thursday.

What gets built first?

Month 1 covers first-version scope and a prototype in front of captains. We agree with Nora and Sam what goes in version 1 and what waits, show a clickable prototype to real captains and customers before any code, and set up accounts in Saltmarsh Charters' name.

What does Saltmarsh Charters need to provide?

20 of the 29 cards include something from Saltmarsh Charters, such as decisions, access or real data, each with a due point. If one arrives late, the cards after it move back by the same amount.

Who uses the charter booking marketplace?

Founder admin: approve new captains after a license and insurance check, watch bookings and fees, and settle disputes. Captain: set their trips and availability once, get booked without phone tag, and get paid out without chasing deposits. Customer: compare captains, see open dates, book and pay a deposit on a phone, and know quickly if weather moves the trip.

Is this a real company?

No. Saltmarsh Charters and everyone in this plan are made up. The format is real: it is how AIwhirks plans and runs every web app build.

More sample plans

Established · 6 months Lantern Hall Venues Venue operations platform Established · 7 months Ridgeway Freight Brokerage Load and carrier operations platform Established · 6 months Halden Equipment Rental Fleet and rental operations platform Established · 5 months Bramble & Oak Veterinary Group Multi-clinic operations platform Startup · 4 months Plotkeeper Community garden management app Startup · 5 months Keystone Tutoring Tutor matching platform Startup · 4 months ShiftSwap Restaurant shift scheduling and swap app

Want a plan like this for your build?

Tell me what you are building and where it is stuck. If it is a fit, the first month starts with a plan like this one, written for your business.

Let's Talk →