Why it exists
The repo is explicit about a no-call workflow: intake happens by form, confirmation happens by email, and deliverables are documented instead of improvised.
Async launch desk / Web operating kit
A quiet operating system for launching small-business sites.
This repo combines a package site, intake desk, template shelf, and handover kit into one repeatable flow. It is built for productized website work where forms and email replace call-heavy setup.
01
What it is
LaunchPack Web Studio is a working system for selling and delivering fixed-scope websites. The public side explains the offers, the intake side captures the brief, and the generator side turns that brief into a prepared client site and handover pack.
Who it helps
It suits solo studios and micro-agencies that want structure for repeatable website launches without rebuilding their process for every client.
What feels specific
The repo includes fixed offers, template choices, upload-aware intake, status tags, delivery-pack generation, and static export notes for simpler builds.
02
Operating surface
The product is strongest when read as a set of connected working parts rather than as a single page or app.
A
Public package desk
The agency site presents three fixed offers, demo portfolio slots, template directions, legal pages, and contact routes.
B
Structured intake
The intake flow records business details, package choice, preferred template, upload assets, and deadline notes, then confirms by email.
C
Template shelf
Three client-site starting points ship with a shared content schema: Clean Modern, Bold Tradie, and Boutique Service.
D
Delivery pack output
Generation does not stop at HTML. The repo also prepares credentials notes, SEO checklists, handover email text, and a site URL placeholder.
03
Dispatch cycle
The repo’s process cadence is simple and observable: scope by intake, confirm by email, build from templates, then hand off with documented deliverables.
- Offer and intake The public site routes clients into a structured intake instead of a booking funnel.
- Review and status Submissions land in the dashboard with searchable records and status tags such as NEW, IN_PROGRESS, and DELIVERED.
- Generate the build A submission can seed a client folder with typed content, template selection, copied assets, and a ready-to-edit starter.
- Ship with notes The handover layer includes deployment notes, invoice helpers, credentials templates, SEO checklists, and handover email copy.
04
Visual notes
No polished screenshots were committed to the repo, so this export uses repo-derived diagrams instead of pretending to show a live marketing capture.
05
Proof and availability
The repo gives enough concrete evidence to describe its scope without inventing usage numbers or launch claims.
Evidence on record
- 3 fixed offers
- Landing Page in 48 hours, Business Website Launch Pack, and Website Care Plan.
- 3 template styles
- Clean Modern, Bold Tradie, and Boutique Service are defined in shared config and template folders.
- 2 working app surfaces
- A public agency site sits alongside an internal intake dashboard.
- Static export path
- Deployment notes explicitly describe a GitHub Pages fallback for Offer A style sites.
Availability notes
- Primary platform: Web.
- Database path: SQLite locally, Postgres-ready via Prisma.
- Email path: confirmation, contact, invoice, and handover templates are present.
- Static fallback: documented for simpler exported builds.
Status: active build
06
Questions
These answers stick to what the repo actually supports today.
Is this a brochure site or an actual workflow tool?
It is both. The repo contains a public package site and an internal dashboard that stores submissions, tracks status, and generates client-site folders.
Does the workflow depend on calls?
No. The repo copy is explicit that intake and follow-up happen through forms and email rather than phone or headset work.
Can it ship static sites?
Yes, within limits. The deployment notes call out a GitHub Pages fallback for Offer A style static exports, while the fuller workflow uses server-side features.
Are real screenshots available?
Not in the checked-in public-safe materials used for this export. The visual section uses diagrams derived from repo structure instead.
Final call
Use this when website delivery needs a system, not a scramble.
LaunchPack Web Studio reads best as an operational kit: offers in front, structured intake in the middle, templates on the shelf, and handover notes at the end.