Solutions 02 Web & Technology
We make “you can edit it yourself” a sign‑off item
Turning your identity into a website you can update yourself after launch.
02
Web & Technology
Timeline
2
weeks
Site Sprint · 4 sign‑offs
The real problem
The website is treated as a project, not an asset
A project has an end date. An asset doesn’t. And the money gets spent in the two years after launch.
How we approach it
The real cost of a website isn’t the build. It’s the two years after launch. So four items on our sign‑off checklist are about you: every page opens in the editor, changing a color doesn’t take outside help (change one token value and the identity and site update together), new sizes take care of themselves, and mistakes get caught.
This makes the start slower. The maintenance contract is separate and you can end it anytime, so what you spend in year two is your choice, not a lock-in.
Before we propose anything, we look at these four things
01
Who edits it, and how often
This question decides the tech stack, not the other way around. Content changes often and non-engineers maintain it ➔ WordPress. Complex features and an engineering team ➔ custom build. We’ll give you a recommendation on the intro call.
02
Is there a restore point?
Most sites don’t have one, or they have backups that have never actually been restored. The only difference between an untested backup and no backup is that you find out later.
03
Are three widths three designs?
Phone, tablet, and desktop aren’t scaled versions of one another. Shrink a layout proportionally and a line on a phone holds ten characters. That’s pushing the problem onto the reader.
04
What the backend looks like
Open a page: do you see a stack of editable blocks, or a locked lump of code? That answer is your maintenance bill for the next two years.
What we ask on the intro call
muzi
Who is going to update this website after it goes live?
You
Someone on our marketing team. The homepage copy changes about once a week.
muzi
Then the tech stack is half decided.
You
I thought that was the last thing to decide.
A rule that makes our job harder
We’ll go through the phase 5 sign‑off checklist with you item by item.
One item is a hard line we set for ourselves: every page has to open in the page editor as a stack of editable blocks, not one big locked lump of code. “It opens” isn’t strict enough. A page stuffed with code opens too.
You get something at the end of every phase
Phases marked “sign‑off” don’t move forward until you’ve signed off.
01
Backups and environment
Set up restore points, confirm hosting and access
You’ll see results of a backup-and-restore drill
02
Foundation
Child theme, design tokens, global settings
You’ll see a one-page sample
Sign‑off: layout direction
03
Layout
Components and page templates
You’ll see one page for each main page type
Sign‑off: revision round 1
04
Content
Content entry, image optimization, multiple languages
You’ll see a full site preview
Sign‑off: revision round 2
05
Final review
Three widths, font loading, performance, backend editability
You’ll see checklist results, item by item
Sign‑off: final review
06
Handoff
Training, documentation, access handoff
You’ll see a handoff meeting + documentation
What you get
We’ll go through the phase 5 sign‑off checklist with you item by item. One item is a hard line we set for ourselves: every page has to open in the page editor as a stack of editable blocks.
Open the backend and you see a stack of editable blocks.
The site The live website, with its production domain, SSL certificate, and basic security. You can edit page structure and layouts yourself in the backend.
Three widths Phone, tablet, and desktop each checked on their own, not scaled proportionally.
Content and search Heading structure, meta descriptions, structured data, sitemap, and indexing settings. Multilingual structure is optional.
Features Forms and notification emails. For e‑commerce, product structure, categories, shipping, and tax rules are optional. Payment integration comes with test cases and notes on error handling.
Operations basics Backups and restore points, including one real restore drill. A performance measurement report and a log of fixes.
Handoff Backend how-to documentation, and a checklist for handing over accounts and access.
See a real example
Click into any of them to see how we made the calls at the time.
Web & Technology work
muzi.tw (this site)
This site was built to this exact spec: a child theme, design tokens wired into the theme, and every page opens for editing in the page editor. A site that can’t do this has to be rebuilt from scratch at its first redesign.
Fixed scope, clear numbers
You’ll get a price range at the end of the intro call. No form to fill out first.
How we charge
Site Sprint (two weeks) or priced by phase
Post-launch maintenance is a separate monthly contract you can end anytime
You pay third-party fees directly. We don’t handle them or mark them up
What we need from you
Access to your hosting, domain, and any third-party services we need
Content: copy, images, product information (tell us up front if you need us to write it)
One point of contact who can make the final call
Three working days set aside for quick replies during final review
What’s not included
Ongoing maintenance and new features (separate maintenance contract)
Copywriting and photography (available as an add-on; see Content & Video)
Running ads and optimizing their performance
License fees for hosting, domains, third-party plugins, and fonts
Account sign-ups and business agreements with third-party systems (payments, logistics, SMS)
What’s involved
CoreWeb DevelopmentApp DevelopmentSupportingVisual DesignMonetization
FAQ
Can I edit it myself once it's done?
That’s one of our hard lines for sign‑off: every page has to open in the page editor as a stack of editable blocks, not locked-down code. At handoff, we train your people until they can make changes themselves.
WordPress or custom build?
It depends on how often it changes and who changes it. If content changes often and non-engineers maintain it, WordPress. If the features are complex and you have an engineering team, a custom build. We’ll give you a recommendation on the intro call.
What if it breaks after launch?
We fix any problems within 30 days of delivery. After that, you can set up a separate maintenance contract or hand it to your own people. We hand over documentation and access cleanly, so you’re not tied to us.
Can you do just the payment integration?
Yes, but first we check whether your site’s structure can support it. Most payment problems come from how order data is handled, not from the payment provider itself.
Book a 30-minute call
It’s free. We’ll ask who will be editing the site after launch, and how often. By the end, you’ll have an initial read on direction and scope.