Scope before the build
The first useful scope is agreed before work starts: what is included, what it depends on, where review happens, and what a later phase would contain.
What gets built, and how it gets agreed
Two sides of one offer. Websites and web apps are the core; AI is added where it is the simplest useful solution to a real task, and left out where it is not.
Websites and web apps
A first business website, a refreshed site for a business that has outgrown an old one or still runs on social profiles, and custom web apps for a recurring workflow.
- First business website, or a refreshed site
- Clear service pages and customer journeys that make contact easy
- Enquiry forms, product or catalogue pages, lead capture and supporting pages where they serve a real user need
- Custom web apps: dashboards, internal tools, customer portals, custom forms and workflow applications
- Launch support covering domain, content, testing, responsive QA, handover and ownership
- Ongoing support is scoped separately and is not implied as included
Practical AI and automation
AI and automation only where they solve a real business task. A simple form, integration or rule is often the better answer, and is used instead when it is.
- Document question and answer over selected sources, with citations or source references where appropriate
- Task-focused agents for a defined intake, draft, lookup or workflow sequence
- AI features inside a web app only when they improve a real workflow
- Integrations, rules, triggers and ordinary automation
- A human stays in charge of consequential actions
When a plain tool is the right answer
Worth saying before anything else. Sometimes the right tool is not AI. A form, an integration or a rule often solves a task more reliably, costs less to run and is easier to hand over. Where that is true, that is what gets built.
How scope, quote and review are handled
No delivery dates, response times or update cadences are published here. Those are agreed with you for your project rather than promised in advance to everyone.
A written quote
The quote covers the agreed scope. It is written, so there is a document both sides can point at rather than a number that changes as the conversation does.
Dependencies are named early
Domain, hosting, content, third-party accounts and access all affect what can happen when. Naming them up front is the difference between a plan and a surprise.
Review against the agreed job
Work is built to be reviewable. How feedback happens is clarified with you rather than promised as a fixed daily or weekly cadence.
Launch, ownership and handover
Domain, content, responsive QA, handover and ownership are settled before launch rather than discovered afterwards.
Ongoing support is separate
If you want support after handover, it is scoped separately. It is not quietly assumed to be included in a build price.
What is not promised
No customer, lead, conversion or revenue result is guaranteed by a website or by an AI feature. Business results depend on the offer, the audience, traffic, follow-up and other factors. What ZUMX commits to is the work, the scope and the handover.
- No customer, lead or conversion figures.
- No revenue, ROI or growth guarantee of any kind.
- No AI accuracy guarantee, certification or security audit.
- No suitability claim for regulated industries.
- No "from" price, fixed timeline or named service region.
What is committed instead
- A written scope, before the build starts.
- A written quote covering that scope.
- Work that can be reviewed against the agreed job.
- Clear handover and ownership at the end.
Read before you write
Two of the four field notes answer whether a website, a custom app, or an AI feature is the right shape of solution, before anyone builds anything.
Field notesBring the problem, not a page list
Email or WhatsApp with what the business needs to do better. Scope and a written quote are discussed before any build starts.