Tell us what needs to change. We will help you scope it.
Start a project →Start with your buyers and the questions sales keeps answering. Leave with approved page templates, an editable build and a launch plan that covers content, performance and ownership.
Be honest here and we will be honest back. Half the companies that call us need a smaller project than they think.
Everything lives in your accounts from the first day: Figma, GitHub, hosting, analytics.
Who visits, what they need to believe, which page does that job.
Tokens, type, components with states, and the rules for extending them.
12-18 templates covering home, services, pricing, proof, resources and conversion.
WordPress blocks or Shopify sections that match the design system one to one.
Every old URL mapped, every redirect tested, rankings protected.
Core Web Vitals, accessibility, schema, forms and tracking verified and signed off.
A 90-minute session and a written guide so your team edits with confidence.
Repository, hosting, domain and analytics in your name, not ours.
Drag the handle. Both states were captured on the same device profile and connection.
Moto G Power · 4G · Lighthouse 12 · Oct 2026Illustrative comparison
You see work every week on a private portal. Nothing moves to the next phase without your sign-off.
| Week | Phase | What happens | Your effort | Gate |
|---|---|---|---|---|
| 1-2 | Discovery | Stakeholder interviews, analytics review, competitor teardown, journey map, sitemap | 3 hours of interviews, access to analytics | Sitemap approved |
| 3-5 | Design | Wireframes, design system, key templates, clickable prototype | Two 60-minute reviews a week | Templates approved |
| 6-9 | Build | Theme or headless build, blocks, forms, integrations, migration script | Content delivery, test logins | Staging accepted |
| 10-12 | Launch | Content load, QA, redirects, performance and accessibility pass, go-live | Final approval, DNS access | Launch checklist green |
Before a pixel changes we export every URL with its traffic and backlinks, decide what stays, moves or retires, and build the redirect map. The new site launches with your rankings intact.
A SaaS website does positioning, product explanation and the demo path. SaaS product UX does onboarding, workflows, roles and states. They need different research and different success metrics, so we scope them as two projects even when one team does both.
Pick the platform at the end of discovery, not before. The design system maps to it one to one.
Every design component becomes a block with locked styles and editable content. Editors can't break the layout.
Section patterns for the pages you add later, so the site grows without new design work.
Self-hosted fonts, responsive images, no page builder, CSS under 45KB per page.
Sections and blocks mirror the design system. Merchandisers compose pages themselves.
Every app justified in writing. We measure what each one costs in load time.
Real test orders through every payment method, shipping rule and discount before launch.
Editors keep the admin they know. The front end is a static, pre-rendered site.
Draft previews with a signed link. Publishing rebuilds only what changed.
Large content sites, strict performance targets, or apps and content sharing one design system.
Tokens as CSS variables, component specs with states, responsive rules, motion notes.
Optional design QA: we compare the build against the system and list what to fix.
Figma files are yours. Any team can build from them, now or in two years.
Numbers arrive in the written proposal. Here is what each scope contains and what moves the price.
What changes the price: number of templates · content migration volume · integrations (CRM, booking, search) · custom blocks · languages · photography and illustration.
Your website should look like the company your customers already think you are. That is the brief we design to.
If this page is close but not quite it, one of these probably is.
Expert review, analytics and Core Web Vitals check, severity-ranked backlog.
S07Custom block themes and headless builds your marketing team can edit without calling a developer.
S17Positioning, pricing page, demo path and the page system around them.
Written for decision makers, tested by our engineers.
Find which server sent the 414 and stop the redirect or form that keeps growing the URL. Raise the nginx or Apache limit only for legitimate long URLs.
Tested on nginx 1.30.6 and Apache 2.4.70 (Apache Lounge Win64 build) on Windows 10 Pro with a Node.js 22.23.4 backend, and WordPress 7.1.4 on PHP 8.3 in Playground, November 11, 2026
What a website costs to build, run and own. See the project line items, vendor prices for hosting, licenses and email, and a worked three-year example.
The decisions to make before a redesign launches. Inventory, keep or remove rules, the URL map, freezes, validation and rollback, with real numbers from our own rebuild.
The line items in a redesign quote and what drives each one. Includes dated market figures with their methods and a worked example from our scoper.
A sample pack links page templates to their content fields, responsive states and launch checks. The completed project includes editable design files, source code and an agreed handover for your team.
A sample pack links page templates to their content fields, responsive states and launch checks. The completed project includes editable design files, source code and an agreed handover for your team.
You keep the agreed project files and source. This sample illustrates the handoff; it is not a client result.
Discovery, page structure, design templates and the agreed platform build are defined in your scope. Content migration, integrations and ongoing care are listed explicitly so the handoff has no hidden assumptions.
The typical website range is six to twelve weeks. The final schedule depends on templates, content readiness, integrations and how quickly your team can review each stage.
We design the publishing workflow around the people maintaining the site. WordPress builds use structured fields or editor-safe blocks rather than unrestricted layouts that can break the design.
Responsive layouts are included for the agreed templates. We check reading order, navigation, forms and overflow at desktop and mobile widths before launch.
We write the copy the build needs: headlines, page sections, calls to action, form labels and messages, from facts your team supplies and approves. Rewriting a large existing content library is scoped separately in the proposal. Blog posts and ongoing content are not part of a build; our sister agency BizAttic runs content and SEO programs.
Template count, custom blocks, content volume and integrations affect the effort. We provide a fixed-scope proposal after discovery and price changes through an agreed change process.
Yes. Your company owns the design files, source repository and accounts from day one. The project can stop at an agreed phase with the completed files staying in your hands.
Our written promise is to fix templates we build that miss the agreed launch checks. The proposal states the measurement method and limits so the result is assessed consistently.
