Proposal standard
Every qualified lead gets a concrete next step, not a vague estimate.
- Scope, timeline, and price range are written down
- Founding-client terms are spelled out when applicable
- Out-of-scope items are named early to prevent drift
Client Process
What working with Beehive actually looks like before you commit.
You should not have to guess whether a studio has a real delivery process. This page puts Beehive's proposal, agreement, QA, and care-plan standards in writing so you can judge the engagement before you book.
First 7 Days
The earliest part of the engagement is designed to remove ambiguity fast.
The goal of the first week is simple: confirm fit, define scope, secure the project, and get content moving without letting the process drift into endless back-and-forth.
-
Discovery call
The first call is a working conversation about your current site, offer, lead flow, budget range, and whether a Starter Site, Growth Site, or care plan is the right fit.
-
A written proposal within 48 hours
If the fit is right, you get a written proposal within 48 hours that spells out scope, timeline, investment, payment schedule, and what is specifically included or out of scope.
-
Agreement + deposit
Projects start with a signed agreement and a 50% deposit. That keeps scope, ownership, revision limits, and launch responsibilities clear before work begins.
-
Build, review, launch
Most Starter Sites target about 3 weeks once content and approvals are moving. Each major milestone includes one revision round, followed by launch QA and a post-launch check-in.
Commercial Standards
The process is built to protect clarity on both sides.
These are the standards behind every Beehive proposal and service agreement. They are published here because trust is easier to give when expectations are concrete.
Scope standard
The engagement is fixed-scope by default so both sides know what is being bought.
- One revision round per major milestone is included
- Extra scope requires written approval before work starts
- Client delays extend timing day-for-day instead of creating confusion
Launch standard
A build is not considered done just because the files are online.
- Launch includes hosting, SSL, analytics setup, and search basics
- Post-launch defects are covered during the initial support window
- The site is expected to be maintainable, tracked, and ready for care
Care standard
Support is structured to keep the site useful after launch instead of letting it decay.
- Care plans cover hosting, monitoring, backups, and routine edits
- Growth work can extend into SEO, landing pages, and paid traffic support
- The recurring relationship is part of the business model, not an afterthought
Payment + Terms
The business side is meant to be plain, not mysterious.
- 50% deposit to start, 50% at launch
- Payments due within 7 calendar days of each milestone
- Founding projects include a 3-month minimum care-plan commitment
- Care plans are month-to-month after any minimum term is complete