Scope of work

Following our Slack conversation, this proposal covers a focused refresh of both sites, each rebuilt as a custom, lightweight site with a unified visual system, hosted on Replit, and structured so you can make easy modifications afterward.

The brief is intentionally tight: brand cleanup, content and navigation structure, UX/UI improvements and polish, migration to custom code, and Replit deployment. The current sideways scroll comes out. The visual direction takes cues from wander.com/os. Both sites read as part of the same visual world.

Because I built the existing versions of both sites, there is no discovery overhead and no archaeology in someone else's codebase. We can move quickly without sacrificing craft.

Shared foundation across both sites

• Unified visual system. One style guide derived from the wander.com/os as the baseline and need to do a deep dive research to build a more comprehensive and signature style for both.
• Brand cleanup. Refining and tightening the existing visual identity, not a full rebrand. Sharpening what's there.
• AI-Native Design System. A robust, lean, AI-native, and reusable set of components built once and shared across both sites, so future modifications stay consistent.
• Replit deployment. Both sites deployed to Replit with environment variables, custom domains, and handoff documentation written for your own future modifications.

Not included in this scope

Naming these explicitly to keep the engagement honest and the scope clean. If any of these become needed, we can scope them separately:

• Full brand identity work (logo redesign, naming, verbal identity).
• New backend functionality — auth flows, payment processing, database migrations beyond what's already in place.
• Long-form content writing or copywriting for new pages (light copy refinement is included).
• Ongoing maintenance, hosting, or support past the 14-day post-launch window.
• Page count beyond ~5 per site. Additional pages can be added with a separate billing.

Timeline

• Week 1Foundation. Unified visual system, IA, content structure for both sites.
• Week 2Design. Both sites designed in Figma, component library defined.
• Week 3–4Build. Custom code, both sites, shared component library.
• Week 5Launch. Replit deployment, QA, handoff docs, 14-day support window.

Total: 4–5 weeks from project kickoff to launch.

Investment

Pricing reflects two custom-coded sites, a shared visual system, and Replit deployment with handoff documentation. This is a meaningful scope increase from previous engagements between us, naming that here so there are no surprises.

What this price reflects

• Custom code, not Webflow or Framer. Hand-written React/Next.js means we own the codebase, the architecture, and the modification path. You can edit it yourself afterward; you're not locked into a platform's editor.
• Shared visual system across both sites. The unified style guide is real design system work, not just two separate Figma files — it's built once and applied consistently so the two sites feel like one world.
• Replit deployment with handoff. Most studios won't touch a custom build on Replit. We will, and the deployment is structured so you can modify, redeploy, and maintain it yourself.
• Existing massivegood functionality preserved. Migrating live functionality from the existing repo into the new build, without breaking what already works.

Payment Terms

• 50% ON KICKOFF$12,000 USD, invoiced on signed agreement. Payable within 7 days.
• 50% ON LAUNCH$12,000 USD, invoiced on sign-off of final build. Payable within 7 days.

Payment Methods

• Bank transfer (USD) — preferred.
• Paypal
• Crypto

Rights & Usage

• Ownership. All design files (Figma) and code (Git) are owned by you on final payment. You can use, modify, and republish them however you'd like.
• Portfolio rights. Blissful retains the right to feature this work in our portfolio and case studies after launch, with reasonable notice to you.
• Revisions. We are flexible about revisions as long as we don't drag the timeline beyond +5 weeks from the original timeline.
• Scope changes. If new requirements come up mid-project, we'll scope and price them separately so they don't delay the core build.
• Cancellation. Either party can cancel the engagement in writing. Work completed up to the cancellation date is invoiced pro-rata against the agreed milestones.
• Post-launch. 30 days of bug-fix support included after launch. Ongoing maintenance available separately if needed.

Next steps

If this proposal works for you, three things happen in order

• Sign-off. Reply on Slack confirming you'd like to move forward. I'll send a short engagement letter for signature.
• Kickoff invoice. $12,000 USD invoice sent within 24h of sign-off. Payable within 7 days.
• Project starts. Within 5 business days of invoice payment. Slack channel set up, kickoff call scheduled, Figma and Git access granted.