Solutions 02 Web & Technology
“You can edit it yourself” is one of our sign-off items
We turn your identity into a website you can edit yourself after launch.
02
Web & Technology
Timeline
2
weeks
Site Sprint · 4 sign-offs
The real problem
The site gets treated as a one-off project
Projects end, but a website gets used for years. Most of the money goes out after launch.
How we approach it
Often, the most expensive part of a website is the two years after launch. So four items on the sign-off checklist test you: every page opens in the editor, color changes don’t need anyone else (change one token value and the identity and site update together), new sizes fall into place on their own, and a wrong edit gets caught.
It makes the early stages slower. Maintenance is a separate contract you can end anytime, and you decide whether to keep paying in year two.
Before we propose anything, we look at these four things
01
Who edits it, and how often
This question decides the tech stack. If content changes often and non-engineers maintain it, we use WordPress. If the features are complex and you have an engineering team, we build it custom. You’ll get our recommendation on the first call.
02
Is there a restore point?
Many sites don’t have one. Or they have backups that have never actually been restored. Whether an untested backup works is usually something you find out the day something goes wrong.
03
Three widths, three designs?
Phone, tablet, and desktop can’t just be scaled up or down. Shrink a desktop layout onto a phone and a line might hold only 10 characters, which is hard going for readers.
04
What the backend looks like
Open a page: do you see a stack of editable blocks, or a wall of locked code? The answer is roughly what you’ll pay in maintenance for the next two years.
What we ask on the intro call
muzi
After launch, who’s going to be updating this site?
You
Someone on our marketing team. The homepage copy changes about once a week.
muzi
Then the tech stack is already half decided.
You
I thought that was something we’d decide at the end.
A rule we find annoying too
We’ll walk you through the phase 5 checklist item by item.
One item is a rule we set for ourselves: open any page in the page editor and you should see a stack of editable blocks. “It opens” isn’t 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 sample page
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, multilingual setup
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 walk you through the phase 5 checklist item by item. One item is a rule we set for ourselves: open any page in the page editor and you should see a stack of editable blocks.
Open the backend and you see a stack of editable blocks.
The site itself A live website on your domain, with an SSL certificate and basic security. You can change page structure and layouts yourself in the backend.
Three widths Checked separately on phone, tablet, and desktop.
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)
The site you’re on right now was built to this spec: a child theme, design tokens wired into the theme, and every page editable in the page editor.
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. They don’t go through us, and we don’t 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?
Yes. It’s one of our sign-off items: every page has to open in the page editor as a stack of editable blocks. At handoff, we keep training your team until they can make changes on their own.
WordPress or custom build?
It depends on how often it changes and who changes it. If content changes often and non-engineers maintain it, use WordPress. If the features are complex and you have an engineering team, build it custom. You’ll get our recommendation on the first call.
What if it breaks after launch?
We handle any issues within 30 days of delivery. After that, you can sign a maintenance contract or hand it to your own team. Either way, we’ll hand over documentation and access cleanly.
Can you do just the payment integration?
Yes, but first we’ll check whether your site’s structure can support it. When payments go wrong, the cause is usually how order data is handled. It’s rarely the payment provider itself.
Book a 30-minute call
It’s free. We’ll ask who will update the site after launch and how often. You’ll leave with a first take on direction and a rough idea of scope.