Process
How an engagement actually runs
This is the real sequence, in order, including what we need from you at each step. Timelines are ranges because they depend on the scope agreed in the proposal and on how quickly content and approvals come back from the client. A single landing page moves faster than a full connected revenue system with multiple integrations.
- 01
Strategy call
Typical timeline: 30 to 45 minutes
This is a conversation, not a sales pitch. The goal is to find out whether a website, a front desk system, or a full connected system is the right starting point, and whether Cellara is a good fit for the business at all.
Cellara's responsibility
Ask about call volume, current site, follow-up process, and where leads go cold.
Client's responsibility
Describe how the business currently gets and loses opportunities.
- 02
Diagnostic
Typical timeline: Same week
The diagnostic identifies specific gaps: pages that do not load fast enough, missing calls to action, no system for following up on a lead, or a site that search engines and AI answer tools cannot read well.
Cellara's responsibility
Review the current site, search visibility, and intake process against what the business actually needs.
Client's responsibility
Share access to the current site and any existing tools.
- 03
Blueprint
Typical timeline: 3 to 5 business days
The blueprint is specific to the business, not a generic package. It lays out what gets built, what it replaces, and what result it is designed to support.
Cellara's responsibility
Put together a written plan covering the pages, features, and systems the business needs and why.
Client's responsibility
Review the recommended approach and ask questions.
- 04
Scope and proposal
Typical timeline: 1 to 2 business days
Nothing is built before scope is agreed in writing. Changes after this point go through a documented change process rather than informal requests.
Cellara's responsibility
Translate the blueprint into a fixed scope, timeline, and price.
Client's responsibility
Decide on scope and sign the proposal.
- 05
Discovery
Typical timeline: 1 to 2 weeks, running in parallel with architecture
This stage is the most common source of delay. The faster a client answers discovery questions, the sooner the rest of the timeline holds.
Cellara's responsibility
Document the business's positioning, offers, and the questions prospective customers actually ask.
Client's responsibility
Answer questions about services, pricing, service area, and audience. Provide existing brand assets.
- 06
Architecture
Typical timeline: 3 to 7 business days
This is where the site's structure and the systems behind it are planned together, so the site is not built as a separate piece from the system that runs behind it.
Cellara's responsibility
Map the pages, navigation, and the system connections between the site, intake, and follow-up.
Client's responsibility
Approve the sitemap and the structure of the intake and follow-up system.
- 07
Design
Typical timeline: 1 to 2 weeks
Design is presented in working pages, not static mockups, so decisions are made against how the site will actually behave.
Cellara's responsibility
Design pages against the approved architecture and the business's brand.
Client's responsibility
Review design concepts and give one consolidated round of feedback.
- 08
Build
Typical timeline: 1 to 3 weeks depending on scope
Larger scopes, custom functionality, and multiple integrations extend this stage. A landing page builds faster than a full connected revenue system.
Cellara's responsibility
Build the approved pages and functionality.
Client's responsibility
Stay available for questions that come up during the build.
- 09
Integration
Typical timeline: 3 to 10 business days
This is what makes the site part of a system rather than a standalone page. Every integration is tested before it goes live.
Cellara's responsibility
Connect the site to the intake system, scheduling, phone and messaging handling, and reporting.
Client's responsibility
Provide access to existing tools that need to be connected, such as a calendar or payment processor.
- 10
Content
Typical timeline: Ongoing from discovery through launch
Content is the other common source of delay. A business that turns around approvals and assets quickly moves through this stage in days rather than weeks.
Cellara's responsibility
Write page copy grounded in the discovery work and the business's actual offers.
Client's responsibility
Supply photos, service details, and any material specific to the business, and approve final copy.
- 11
Testing
Typical timeline: 3 to 5 business days
Nothing goes live until forms submit correctly, calls route properly, and the site performs on both desktop and mobile.
Cellara's responsibility
Check forms, calls to action, page speed, mobile behavior, and every system connection.
Client's responsibility
Test the site and system as a real prospective customer would and report anything that feels off.
- 12
Launch
Typical timeline: 1 business day
Launch is treated as a checklist, not a moment. Analytics, forms, phone routing, and search indexing are all verified after go-live.
Cellara's responsibility
Publish the site, confirm domain and tracking are correct, and confirm every integration is live.
Client's responsibility
Approve the final site and system for go-live.
- 13
Optimization
Typical timeline: Ongoing
A launched site is a starting point. The optimization relationship covers ongoing search visibility, reputation processes, and adjustments as the business changes.
Cellara's responsibility
Review performance, recommend adjustments, and maintain the technical and search work over time.
Client's responsibility
Share what is and is not converting from the business side.
Start with a strategy call
We will tell you honestly which stage your business needs to start at, and what the timeline looks like for your specific scope.
Book a Strategy Call