Support, scoped and quoted.

Yes. After launch, further work is scoped and quoted when you need it: fixes, updates, new pages, app releases or growth work. Each round has a written scope, a deposit to start and the balance before it ships.

You know what we are working on and why. Nothing recurs on its own and there is no standing charge between rounds. Larger features or campaigns are scoped before they begin.

Support is quoted per piece of work, not sold as a standing plan. A round can cover maintenance, bug fixes, content changes, new pages, app releases, search work or improvements to the inquiry flow.

Each quote defines the scope, priorities and response expectations. Hosting, third-party fees, advertising spend and larger builds are called out separately. You get a clear scope rather than an open-ended promise to do everything.

We look at the whole path: how someone finds you, what convinces them, whether they complete the inquiry, and how your team follows up. That gives us a practical list of improvements, from stronger service pages to shorter forms and better routing.

When you bring us back for growth work, we agree on tracking and review lead quality with you. The next round of work follows that evidence, rather than publishing more pages just to fill a report.

We agree on the actions that matter to your business, such as qualified inquiries, booked calls, purchases or active app users. Where the tools allow, we connect those actions to their traffic sources and establish a starting point.

Reports should explain what changed, what we learned and what to do next. Revenue attribution depends on your systems and follow-up, so we are clear about what the data can and cannot show.

Security is part of the build scope. Depending on the app, that includes secure sign-in, server-side permission checks, protected credentials, validated inputs and controls against automated abuse. We decide what each user can access and keep sensitive information out of public pages and logs.

Payments, backups, monitoring and data retention are planned around the product. If your business needs a formal security review or specific compliance requirements, we scope those explicitly before development.

Often, after a technical review. We need to understand the code, hosting, integrations, account access and any unresolved problems before promising support.

We then separate urgent repairs from routine care and future improvements. If the foundation needs substantial work, you get that assessment before we quote any support.

No. The build is a defined project: a deposit to start, the balance before launch, then handover. Support afterwards is a separate decision, quoted when you need it.

We explain what needs attention after launch and which costs continue either way, such as hosting and subscriptions. If we keep working together, each round gets its own written scope and handover.

Ownership and handover are written into your agreement, including the custom code, design files and documentation covered by the project. We plan domain, hosting and developer accounts around your ownership and access.

Third-party software keeps its own licensing terms. We explain those dependencies and ongoing costs, so you know what you control and what you are subscribing to.