For WordPress developers
The build pays once. The care plan pays every month — if it's defined.
WordPress work comes in two shapes. There's the build: a theme or page-builder site, plugins, content entry, hosting set-up and launch. Then there's everything after: updates, backups, security, the plugin that breaks after an update, and the client who emails 'can you just add a page' every few weeks. The build is usually quoted; the after is usually where the hours disappear.
ApeiroCraft sends both as proposals: a build with clear limits on pages, content entry and premium plugin licences, and a care plan that says exactly what maintenance covers and what's new work. You see when each is opened and reopened, the client signs in the browser, and invoices come from the accepted proposal.
Where WordPress work leaks hours.
Content entry nobody counted
The client sends forty pages of copy in Word documents, half without images, two weeks before launch. Formatting it was never in the quote.
Plugin licences and hosting
Premium plugins licensed on your account, hosting under your card. When the client leaves or stops paying, untangling who owns what is a week of admin.
'Maintenance' as free development
The care plan covers updates and backups — and somehow also new forms, a booking plugin and a redesign of the footer, because nothing said otherwise.
Build, launch, maintain — each one signed.
Care plans as their own proposal
Tier your care plans by what's included — updates, backups, uptime checks, a number of small changes — and send the right tier as a separate proposal after launch.
See when they've read it
Opens and re-opens are recorded on the link. A care-plan proposal opened right after launch, then left, is worth a quick follow-up while the site is fresh in their mind.
Signed scope and ownership
The signature records name, email, IP address and a UTC timestamp and can't be changed — so who owns the hosting and licences is on record.
Build milestones and monthly invoices
Convert the accepted build proposal to a deposit invoice and later the launch invoice. Care-plan invoices go out monthly against the same client record.
What a WordPress proposal has to include.
A WordPress build is easy to quote and hard to finish. These sections make finishing possible.
Pages and templates
If it's left vague
A 'small site' grows to thirty unique layouts.
With ApeiroCraft
List page templates designed and the number of pages you'll build from them.
Content entry
If it's left vague
You end up formatting the client's copy and sourcing images.
With ApeiroCraft
Say whether you enter content, how many pages, in what format it must arrive, and by when.
Plugins, licences and hosting
If it's left vague
Licences and hosting sit on your accounts indefinitely.
With ApeiroCraft
State which premium plugins are needed, whose account they're on, and who pays hosting.
Care plan inclusions
If it's left vague
Every request is treated as maintenance.
With ApeiroCraft
Define updates, backups, monitoring and included small changes, and what counts as new work.
Fixes after updates
If it's left vague
A plugin conflict after an update is expected to be fixed free, forever.
With ApeiroCraft
Say how breakages from updates are handled inside the plan and outside it.
- Build and care-plan proposals on one client record.
- Monthly care-plan invoices with your own payment link.
- Team notes for where logins live, plugin lists and hosting details.
Common questions.
How do WordPress developers usually price their work?
Builds are commonly fixed-price with a deposit and a launch payment, or packaged by size. Ongoing work is usually a monthly care plan in tiers, sometimes with included hours, plus an hourly or day rate for new work outside the plan. ApeiroCraft holds the structure you use; it doesn't suggest rates.
What does a care plan proposal look like?
Three tiers. The middle one: weekly plugin and core updates, daily backups kept for a stated period, uptime monitoring, security scanning, fixes for breakages caused by updates, and a small number of content changes a month. New features, redesigns and new plugins quoted separately. A minimum term and notice period. The client signs after launch and you invoice each month from their record.
When is ApeiroCraft not the right fit for a WordPress developer?
It doesn't connect to WordPress, monitor sites, run updates or track support hours, and it won't charge cards automatically each month. Developers who sell many small care plans often prefer a tool with automatic recurring billing. ApeiroCraft fits builds and care plans where a signed scope matters.
Should hosting be in my name or the client's?
Either can work — the important thing is that the proposal says which. If you resell hosting, say what's included and what happens if the client leaves.
Which template should I start from?
The website maintenance template for care plans — tiers, tasks, response times, and what counts as new work — and the web design template for builds.
Sign the care plan, not just the build.
Start from the website maintenance template and send your first tiered care plan.
Start freeStill deciding? Talk to the founder
Keep reading
Free template
Website maintenance proposal template
Care-plan tiers, response times, included hours, and a clear line between upkeep and new work.
Free template
Web design proposal template
Goals, scope boundaries, week-by-week process, and staged pricing that stops scope creep.
Solution
ApeiroCraft for freelance developers
A scoped SOW with an exclusions list, signed in the browser and invoiced by milestone.