Theme and blocks
Custom block theme, theme.json tokens, locked patterns, custom blocks for your content types.
[ Platform · WordPress ]WordPress development services
WordPress, built like software, not like a template.
Custom blocks, a controlled plugin stack and a publishing workflow your marketing team can use. Choose a conventional WordPress build or a headless setup when the requirements justify it.
Typical timeline4-12 weeks
ApproachBlock theme or headless
HostingManaged, your account
EditorsGutenberg, locked blocks
PerformanceCWV pass at launch, guaranteed
AfterCare plan, updates on staging
Plugins per site ≤ 12CSS per page < 45KBLCP target ≤ 2.0sUpdates Staging firstBuild standards on every WordPress project
[01]Platform fit
When WordPress is the right call, and when it isn't.
We build on three platforms, so we have no reason to push this one. Here is the honest test.
Good fit if
- Your team publishes content often and needs clear editing controls
- You need custom blocks or a structured content model
- You can maintain hosting, staging and access ownership
Not a fit if
- A simple hosted template already meets the brief
- You need headless architecture without a reason for the extra operations
- Your core requirement is a complex application workflow
[02]Scope by area
What a WordPress build covers here.
Every item below appears in the proposal as included, excluded or optional. No surprises in week six.
Content model
Post types, taxonomies and fields designed for how your team actually publishes.
Plugins
A short, justified list. SEO, forms, security, caching. Each one reviewed for performance and maintenance cost.
Forms and CRM
Spam-resistant forms, HubSpot or Salesforce sync, booking embeds, consent handling.
Performance
Image pipeline, font strategy, caching layers, a budget per template enforced in CI.
Hosting and security
Managed host in your account, 2FA, hardened login, backups with restore tests, uptime monitoring.
On-page SEO
Clean markup, schema, sitemaps, redirects, canonical rules. The foundation BizAttic builds on.
Handover
Repository, documentation, recorded training, and a care plan if you want one.
[03]Classic or headless
Two ways to build it. We'll recommend one.
Most marketing sites are best served by a well-built block theme. Headless earns its extra cost in specific situations.
What you get
- One system: editing and rendering in WordPress
- Lowest ongoing cost and the widest talent pool
- Fast when built properly: under 45KB CSS, no builder
- Live preview exactly as published
Right for
Marketing sites up to a few thousand pages, teams without front-end developers, budgets that favor maintenance simplicity. Timeline 4-10 weeks · Care: Essential or Professional tier
What you get
- WordPress stays the editor; the front end is pre-rendered
- Per-route code splitting, image optimization, edge caching
- Draft previews with signed links, publish-time rebuilds
- Same design system shared with an app or portal
Right for
Large content sites, strict performance or security requirements, or companies whose app and website need one design system. This site is built this way. Timeline 8-16 weeks · Care: Professional or Growth tier
[04]Migration and replatforming
Move hosts, themes or platforms without losing a ranking.
The redirect map is the product. We build it first, test it on staging and watch it for two weeks after launch.
Inventory
Every URL exported with traffic, backlinks and rankings. Nothing is retired without a number next to it.
Map and migrate
Content moved by script, not by hand. Media, authors, categories, custom fields and SEO data all reconciled.
Launch and watch
Redirects tested before DNS changes. 404s, coverage and Core Web Vitals monitored daily for 14 days.
100%Of legacy URLs mapped before launch
0Redirect chains allowed at launch
14Days of post-launch monitoring, included
1Rollback plan, rehearsed before go-live
[05]Inspectable artifact
Our launch checklist, as we run it.
A sample with illustrative values. Yours carries your real numbers.
| # | Check | Tool | Result | Status |
|---|---|---|---|---|
| P-01 | LCP on home, service and post templates (mobile, 75th percentile) | Lighthouse CI + CrUX | 1.3s / 1.4s / 1.2s | Pass |
| P-04 | CSS per template under 45KB gzipped | Build report | 31KB max | Pass |
| S-02 | All 1,146 legacy URLs resolve with 200 or a single 301 | Redirect checker | 1,146 / 1,146 | Pass |
| A-03 | Keyboard and screen-reader pass on forms and navigation | axe + manual | 0 critical | Pass |
| F-01 | Booking and contact forms deliver to inbox and CRM | Test submissions | 4 / 4 received | Pass |
| B-02 | Backup restored to a clean environment within 20 minutes | Restore drill | 14 min | Pass |
[06]Engagement models
Scoped by what you bring.
Prices arrive in the written proposal. What changes them: templates, custom blocks, migration volume, integrations, WooCommerce.
Scope A · Build only
You bring approved designs
4-8weeks
- Technical review of the designs
- Block theme and custom blocks
- Forms, SEO foundation, hosting
- Launch checklist and training
Scope B · most chosen · Design + build
Full WordPress project
8-12weeks
- Discovery and design system
- Block theme with 12-18 templates
- Migration with redirect map
- Launch checklist, training
- 30 days of post-launch fixes
Scope C · Headless
Headless WordPress
10-16weeks
- Everything in Scope B
- Pre-rendered front end, previews
- Performance budget in CI
- Documented component library
[07]Concept
Fourteen locations, one editor, no page builder.
A concept for a multi-location practice: a block theme with online booking and location pages an office manager can update without a developer.
Read the case[08]Adjacent
Bigger, smaller or different?
Three doors next to this one.
S10
WooCommerce Development
WordPress stores with tested checkout, a short plugin list and updates run on staging first.
S15Speed Optimization
Core Web Vitals work measured in the field, not just in Lighthouse.
S14Website Maintenance and Care Plans
Updates on staging first, restore drills, monitoring, a monthly report.
[09]Sample handoff
WordPress launch QA checklist
The sample checklist covers editing permissions, backups, forms, redirects and template performance. Each launch records the checked environment and leaves a rollback route rather than relying on a plugin score alone.
Sample · scope agreed before work starts
WordPress launch QA checklist
The sample checklist covers editing permissions, backups, forms, redirects and template performance. Each launch records the checked environment and leaves a rollback route rather than relying on a plugin score alone.
You keep the agreed project files and source. This sample illustrates the handoff; it is not a client result.
[10]Questions
WordPress questions, answered straight.
Do you use page builders?
Our core offer uses custom blocks, structured fields and a design system. The proposal describes the editor your team will use rather than assuming a page builder is the right fit.
When is headless WordPress appropriate?
Headless can fit a site that needs a separate frontend and has the capacity to operate it. We compare previews, hosting, publishing and rebuild requirements before recommending the added complexity.
Can you work from our Figma designs?
Yes. We review the layouts, component states and content model before estimating the build. Missing mobile or interaction states are resolved before implementation.
Can you replace a slow or fragile theme?
We first inspect the causes of the problem. A theme rebuild is scoped only when fixes to assets, templates, plugins or hosting would not meet the requirements.
How are plugins selected?
We document what each plugin does and avoid overlapping tools. Licensing, updates and any third-party costs are identified for the owner before the build is approved.
How do you protect the editing experience?
We define roles and structured fields, test common publishing tasks and keep layout controls bounded. Your handoff includes the source and instructions for the agreed editing workflow.
Do you handle WordPress migration?
Yes, with a content inventory, URL decisions and a tested cutover plan. Complex migrations get their own reconciliation checklist and rollback conditions.
Can you look after WordPress after launch?
A care plan can cover staging updates, tested backups, monitoring and a monthly report. The response windows and included work are agreed in writing.
[11]Next step
Tell us about the site you have and the one you need.
- 01 · TodayInstant confirmation and a booking link.
- 02 · 1 business dayA senior engineer replies personally.
- 03 · 5 business daysWritten, fixed-scope proposal.