The practical things, without the small print taking over.
?Clear.
Getting started.
An idea is enough.
I design and build bespoke websites, practical automations and custom software. Some projects solve one repeated task. Others bring a whole working process together.
Often, yes. I look at what you use, what needs to connect and where the friction is. A focused integration can be more useful than replacing everything.
Yes. We can agree a useful first version and leave room for later work. I’ll help separate what you need now from what can wait.
A short description of the problem is a good start. A current website, a few references or a rough timeframe can help. We agree the scope and timing around the actual work, content and dependencies.
Costs & ownership.
Clear before we build.
I quote privately for the agreed scope. The content, functionality, integrations and level of custom work all matter. We establish the approach and responsibilities before work starts.
There can be. Domains, hosting, APIs and other platforms may have their own charges. I explain the relevant running costs separately from the build and any optional maintenance.
We agree the handover, account access and ownership as part of the project. Third-party products and licences keep their own terms. I make those distinctions clear rather than promising rights I cannot transfer.
Website builds include foundational on-page and technical SEO. Advanced SEO is a separate scope, which can be a one-off project or ongoing work. I don’t promise rankings, traffic or sales.
We go through the agreed deliverable, relevant access, documentation and next steps. How you run the build afterwards is part of that conversation.
Yes. Monthly maintenance is available by separate arrangement and is completely optional. The scope, price and responsibilities are tailored to your build.
We can discuss a separately scoped improvement when the need arises. New features are not automatically included in maintenance; we agree what the work involves first.