Inquiries that do not wait for the build
Every inquiry is a deal on the pipeline with its next step, and you email from the record through Gmail, so the next lead gets an answer while you are deep in a build.

A website is four weeks of design and three weeks of waiting for the client’s copy. Flori keeps the inquiry, the discovery notes, the sitemap and every round of feedback beside the client they belong to, and shows exactly what is holding up the launch.

Fig. 1 · DemoKestrel Labs launch site, week four
The design was approved in week two. In week six you are still building with placeholder text because the About copy and team photos are “almost ready”.
The proposal said two revision rounds. Feedback comes by email, a Figma comment and a voice note, and nobody can say which round this is.
Nobody has the domain registrar login, the contact form sends to an old inbox, and the old site’s URLs have no redirects.
Every inquiry is a deal on the pipeline with its next step, and you email from the record through Gmail, so the next lead gets an answer while you are deep in a build.

Start each site from the website project template and add your phases: discovery, sitemap, wireframes, design, build, launch. Design waits on the approved sitemap in the plan, and the brief and sitemap live in Docs on the project.
Project templates: Core and up
Each piece of content the client owes is a task set to Waiting, with the date you asked. You see exactly what is holding the build, and you can publish the same list to the client page, so the talk about the launch date is about facts.
Publish each design round to the client page and the client approves it from one link. Name the round in the deliverable and log time on revision tasks, so when round three arrives you can show what the proposal covered and what the extra round took.
Client pages: Core and up
Fictional example: A $9,500 site, built by a solo designer.
The last of the copy arrives. The Waiting tasks close and the final build tasks move to in progress.
Pre-launch checks as tasks: redirects from the old URLs, a test of every form, analytics, favicon.
DNS switch in the morning. If the site deploys from GitHub, the deployment shows on the project (Core).
Claude drafts the handoff doc from the project: where the CMS logins live, a short training video, care plan options. You publish it to the client page.
Free covers 3 active projects and 200 customer records, enough for your first clients. Core adds unlimited projects, project templates, client pages for approvals and forms for new inquiries.
Core $12 per person a month, or $10 billed yearly
Start freeNo. Design in Figma and build in Webflow, WordPress or code as you do now. Flori holds the client, the plan, the content you are waiting on and the approvals. Publish a finished design or a link to it on the client page.
Yes. The website project template covers preparing, building and reviewing a site with a launch checklist. Add your discovery, sitemap and revision round steps once, and every new site starts from them.
Write the number of rounds into the scope, publish each round to the client page as its own deliverable, and log time on revisions. Start the scope from the statement of work template.
Free covers 3 active projects. Core is $12 a month, or $10 billed yearly, for unlimited projects, templates and client pages. Clients are free on every plan.