A focused business website is our core service. Shops, portals and custom workflows are also projects we can scope. “Separate scope” means a different brief and quote—not a polite way of saying no. Specific integrations are assessed before we promise compatibility.
01 / Explain & convert
Win a useful inquiry.
A business website, a focused service page or a campaign landing page. Give someone a reason to care and a sensible way to respond.
Core build / within agreed page count
What we can build
Offer-led pages, a clear customer journey and standard inquiry capture. An additional campaign-page program, branching qualification form or complex lead routing gets its own scope.
What it depends on
Your offer, your content and where inquiries should go. Advertising, ongoing optimization and lead-volume guarantees are not bundled into the website.
02 / Sell & get paid
Make the sale. Take the payment.
A shop, a service purchase, a deposit or a subscription. “Buy now” should have an actual plan behind it.
Additional scope + provider costs
What we can build
Product or service buying journeys, checkout connections and the agreed customer confirmations. Catalog size, delivery rules, currencies, subscriptions and order handling shape the project.
What it depends on
An appropriate commerce or payment provider, your merchant account, product information and your selling terms. Transaction fees and platform subscriptions are separate costs. We do not decide tax treatment on your behalf.
03 / Book a place or a person
A calendar. With fewer emails about calendars.
Appointments, consultations, classes and events. Let the booking route reflect the way your operation actually works.
Simple connection by agreement / custom rules scoped
What we can build
A clear route into a suitable existing booking service. Custom availability, multiple staff, resources, deposits, cancellation rules or event capacity need more detailed scoping.
What it depends on
The provider’s supported features, your account, real availability and a working confirmation process. Paid provider features are not silently included in our build fee.
04 / Give customers their own space
“Just add a login.” Famously the whole specification.
Members, clients or staff may need different access to different things. That is a product decision, not a decorative padlock.
Custom project scope
What we can build
Member areas, client portals, gated resources and account-based workflows. We define roles, permissions, recovery, administration and the actual tasks people need to complete.
What it depends on
The data involved, access rules, suitable infrastructure and an agreed support plan. Sensitive records, complex permissions or regulated workflows need an appropriate specialist review. A login screen alone is not a security design.
05 / Keep it current
Change a sentence. Without opening a diplomatic incident.
Articles, projects, resources and ordinary page updates. Decide what your team needs to edit before we choose how editing should work.
Editing setup agreed / larger content systems scoped
What we can build
Editable content areas, blogs, portfolios and structured resource libraries. Large archives, approval workflows, directories, multilingual content or advanced search need additional planning.
What it depends on
The selected platform, who will maintain the content and any relevant licenses. We distinguish content editing from layout changes or new functionality at handover.
06 / Connect the business
Stop employing copy and paste as your operations team.
Let information move between the website and the systems you use—where the connection is supported and actually useful.
Integration scope + possible provider costs
What we can build
Connections to CRM, email, analytics and other agreed tools. We define which information moves, where it goes, permissions, consent where applicable and what happens when a connection fails.
What it depends on
Supported APIs or integration methods, appropriate access and provider limits. “It has an API” is the beginning of an assessment, not a promise that every workflow is available for free.
07 / Replace what is there
A new website. Not an accidental bonfire.
Keep what is useful. Replace what is not. Check the domain, email, existing pages and connections before changing things.
Rebuild plan / migration effort scoped
What we can build
A redesigned site with an agreed content and migration plan. We identify existing URLs, useful content and services that need preserving, then plan the changeover and relevant redirects.
What it depends on
Access to the current setup, export options and the size of the site. Large migrations, mailbox moves and complex platform changes are separate work. No responsible rebuild promises that search rankings cannot change.
08 / The more involved thing
Not a brochure? Good. Tell us what it needs to do.
Dashboards, quoting tools, directories, workflows and application-level projects. We can have that conversation too.
Discovery & custom project scope
What we can build
We can scope an application or workflow around its users, decisions, data and operating requirements. The first deliverable may be a specification or a focused prototype before a full implementation is quoted.
What it depends on
Feasibility, data access, permissions, maintenance and any specialist requirements. A complex product is not squeezed into a five-page website price by calling every screen a page.
“Any” is an invitation. Not a blank check.
We can assess the unusual brief. If a feature needs its own scope, a paid platform or specialist input, we say so before agreeing the build. If it is not a sensible fit, we say that too.
What needs to happen when someone visits? Start there. We will work out the sensible way to build it.
“Can it also…?”
Tell us what it needs to do. You don’t need to know what the feature is called. We’ll explain what fits, what needs its own scope and what depends on another system.
Rough notes are welcome. Passwords, customer records and confidential files are not needed to start this conversation.