Bolt Case Study: How a Two-Person Agency Delivered 5 Client Landing Pages in One Week Using AI
Case Study: From Overwhelmed to Overdelivering — A Two-Person Agency’s Bolt Workflow
When freelance designers Maya and Jordan launched their micro-agency, they never expected to land five landing page contracts in the same week. With traditional development workflows, delivering all five on time would have been impossible. By adopting Bolt as their core AI-powered development platform, they shipped every project — with custom domains, client previews, and polished components — in just seven days. This case study breaks down their exact workflow, tooling, and the Bolt features that made rapid multi-client delivery a reality.
The Challenge
- 5 clients, each needing a unique branded landing page- 7 calendar days from kickoff to live deployment- 2 team members — one designer, one project manager (no dedicated developer)- Each client required a custom domain, mobile responsiveness, and a real-time preview link for feedback rounds
The Solution: Bolt-Powered Rapid Delivery
Step 1 — Project Scaffolding with Bolt
Maya created all five projects inside Bolt on Day 1. Each project started from a single prompt describing the client’s brand, industry, and desired sections.
Prompt example (Client: GreenLeaf Wellness):
“Create a modern landing page for an organic skincare brand called GreenLeaf Wellness. Include a hero section with a headline and CTA button, a three-column feature grid highlighting natural ingredients, a testimonial carousel, a pricing table with two tiers, and a footer with social links. Use an earthy green and cream color palette.”
Bolt generated a full React + Tailwind CSS project with working components in under 60 seconds per client.
Step 2 — AI-Generated Components and Customization
Rather than building every section from scratch, the team used Bolt’s iterative prompting to refine components. Here is how they adjusted a pricing table after initial generation:
Follow-up prompt:
“Update the pricing table: rename Tier 1 to ‘Essentials’ at $29/month and Tier 2 to ‘Premium’ at $59/month. Add a highlighted ‘Most Popular’ badge on Premium. Make the CTA buttons rounded with a hover scale effect.”
Bolt applied the changes inline, preserving the existing layout and styles. The resulting component code looked like this:
Essentials
$29/mo
Most Popular
Premium
$59/mo
Preview URL format:
https://bolt.new/~/projects//preview Clients could view the live page on any device and leave comments. Jordan tracked feedback and translated it into follow-up prompts, closing the feedback loop in minutes instead of hours.
Step 4 — Custom Domain Deployment
Once each client approved the final version, the team deployed directly from Bolt. For custom domains, they configured DNS as follows:
DNS Configuration (per client):
Type: CNAME
Name: www
Value: cname.bolt.new
TTL: 3600
Type: A
Name: @
Value: 76.76.21.21
TTL: 3600
Inside Bolt’s deployment settings, they linked each project to its respective domain:
Bolt Deployment Settings:
- Open project → Settings → Domain
- Enter custom domain: www.greenleafwellness.com
- Click “Verify DNS” → Wait for propagation (typically 5-30 minutes)
- Enable HTTPS (auto-provisioned via Let’s Encrypt)
Click “Deploy to Production”All five sites were live with SSL certificates within a single afternoon.
The Results
| Metric | Traditional Workflow | Bolt Workflow |
|---|---|---|
| Avg. time per landing page | 3-5 days | 1-1.5 days |
| Client feedback turnaround | 24-48 hours | Under 1 hour |
| Deployment setup time | 2-4 hours (hosting, CI/CD) | 15 minutes |
| Developer headcount needed | 1-2 dedicated devs | 0 (designer + PM only) |
| Total project cost reduction | Baseline | ~60% lower |
DNS verification fails after adding CNAME
Cause: DNS propagation can take up to 48 hours depending on the registrar. Some registrars also require you to remove conflicting A records before adding a CNAME on the root domain. Fix: Wait 30 minutes and retry verification. If it still fails, check for conflicting records in your registrar’s dashboard and ensure there are no typos in the CNAME value.
Preview link shows a blank page
Cause: A syntax error in a recent prompt edit may have broken the component tree. Fix: Use Bolt’s error overlay to identify the broken component. Prompt Bolt with: “Fix the current build error and restore the last working state.”
Styles look different on mobile preview
Cause: Tailwind responsive breakpoints may not have been included in the initial prompt generation. Fix: Add a follow-up prompt: “Make all sections fully responsive. On mobile, stack columns vertically, reduce heading font sizes by one step, and add horizontal padding of 1rem.”
Frequently Asked Questions
Can a non-developer really build production-quality landing pages with Bolt?
Yes. Bolt generates clean, standards-compliant React and Tailwind code from natural language prompts. The case study above demonstrates that a designer with no coding background successfully delivered five client-ready pages. For simple landing pages, no manual code editing is required. For more complex interactivity, basic familiarity with HTML or React helps during refinement.
How does real-time client preview sharing work in Bolt?
Every Bolt project has a shareable preview URL that reflects the latest saved state of your project. When you share this link with a client, they see a fully rendered version of the page in their browser — no login or account required. As you make changes and save, the preview updates, enabling rapid feedback cycles without any deployment step.
What happens if a client needs changes after the site is deployed to a custom domain?
You can continue editing the project in Bolt at any time. Once changes are finalized, simply redeploy from the project settings. The custom domain and SSL configuration persist, so the update goes live within minutes. For agencies managing multiple sites, this eliminates the need for separate hosting dashboards or CI/CD pipelines.