Five phases. Three formal client gates between them. Dependencies and assumptions named below — so we know in week one what TSPEC owes us, what we owe TSPEC, and where the timeline can flex without snapping.
From kickoff to public launch. Excludes pre-kickoff contract administration.
Discovery · Wireframes · Visual Design · Development · QA & Launch.
Formal sign-offs at strategy, wireframes, and design. No surprises post-build.
Bug-fix and tweak window, included in project price. No additional invoice.
04.1 · The picture
Targeting kickoff: week of June 1, 2026
04.2 · Phase by phase
The two weeks where we listen, audit, and align. No design happens until we agree on what we're solving and for whom. Two journey workshops, one tspec.com audit, one strategy brief, one signed-off IA.
End of week 2. TSPEC approves the strategy brief, dual-journey personas, and IA in writing. Wireframes don't start until this is signed.
Lo-fi wireframes for every page template at desktop and mobile. The "shape" of the site — no colors, no photography — so feedback focuses on structure, hierarchy, and conversion logic before visual design enters the conversation.
End of week 4. TSPEC approves the wireframe set in writing. Visual design unlocks. Dev environment provisioning begins in parallel.
Color, type, photography, motion. The brand-on-screen pass. Homepage concept first; once approved, the full template library follows in a single sprint. Component library doubles as the dev handoff spec.
End of week 6. TSPEC approves the design system and homepage. Build accelerates — no more design changes without a written change order.
WordPress custom theme on Gutenberg, hand-written front-end, ACF for structured content. Content migration runs in parallel from week 6. Forms, Calendly, GA4, RankMath wired and tested as features land. Internal QA continuous.
Weekly Loom-style walkthroughs of the staging build. Async feedback collected through your project manager, batched, never blocking dev velocity.
Two weeks of polish, accessibility, and launch prep. Real-device QA matrix, axe + manual screen-reader pass, performance optimization. Then training. Then go-live. Then we're on call for 30 days.
Coordinated DNS cutover during a low-traffic window. Pre-flight checklist on the call. 30-day support window starts the moment we cut over.
04.3 · Honesty about the calendar
One named individual with authority to consolidate feedback and sign at gates. Without this, gates take twice as long and three opinions split decisions.
4–6 stakeholder interviews scheduled within the first week of kickoff. Calendars locked at contract signature.
Existing logo files, photography library, customer testimonial videos, RCDD/BICSI cert artwork. Whatever's available in your DAM or Dropbox.
Kinsta hosting, Calendly account, Gravity Forms license — all created in TSPEC's name within week 2. We help; you click "create account."
Feedback at gates within two business days. Beyond that, the timeline shifts day-for-day. Not punitive — just physics.
Per RFP, we restructure existing copy onto the new IA but write no new copy. If a section needs to be net-new, that's a change order.
We'll source 1–2 stock images if a section is critically under-illustrated. A full photo shoot is out of scope (and budget).
Forms route to email and optionally to a CRM via Zapier or native webhooks. Building a custom Salesforce/HubSpot integration is a separate engagement.
English only. Multilingual is a meaningful scope addition; happy to quote separately if it's on the roadmap.
Round 1 + Round 2 at wireframes; Round 1 + Round 2 at design. Round 3 = change order. Predictable, never surprising.
04.4 · Key dates
This document delivered to Stephanie Raymer at Raymer Solutions before the 5:00 PM ET deadline.
Raymer Solutions reviews submissions. Available for written clarifying questions via email — same-business-day response.
Per RFP §5. We have a contract template ready and can return it signed within 48 hours of receipt.
Contract execution, deposit invoice, account creation (Kinsta, Calendly, Gravity Forms), stakeholder interview scheduling.
Discovery begins. Kickoff workshop with TSPEC + Raymer Solutions on a mutually agreed date that week.
End of week 4. Visual design unlocks.
End of week 6. Build accelerates.
End of week 10. DNS cutover during low-traffic window. 30-day support window opens.
Post-launch tweaks and bug fixes complete. Optional Care or Care+ retainer begins if elected.