Samuel Mfinanga · Named engineer · 20+ years infrastructure
Website Delivery · project start
Start your website brief.
Tell us what the site needs to accomplish. Answer what you know; every question is optional. Your choices create an editable draft on Contact; nothing is sent until you review and submit it there. This is a scoping request, not a booking, quote, or automatic build. Do not enter passwords or private records.
Built on a documented code, data, hosting, and security stack
Speed and search are part of the handoff
After launch
We can keep the site, or leave you a site you do not have to babysit
Care is a choice. It is not a surprise invoice
Website Delivery: what this includes
Website Delivery: the work in scope.
01The jobWhat a visitor must be able to do. Not a stack of references with no decision.
02The handoffHost is on. You are not the webmaster. If you want us to stay, that is a separate yes.
Website Delivery: the practical distinction
What changes when this work is done here.
A template you then have to run.
A site we build, and can keep.
Search added later, for a fee.
Speed and search are in the handoff.
The workflow
How a site gets built
01The job of the siteWhat a visitor must be able to do. Not a stack of references with no decision.
02The buildDesign, then a documented build, data layer, hosting, and security setup. You are not the webmaster.
03The launchHost is on. Speed and search are part of the handoff, not a later invoice.
04Care, if you want itWe keep the site, or you keep a site you do not have to babysit. Either way it is not a template.
Start with the site’s job
Four different briefs. One accountable site.
A new site, a redesign, and a broken lead path are different projects. Pick the job that matters first; the written scope should say how the result will be checked.
01
Explain a complex offer
Can each kind of buyer find the service, proof, and next step meant for them?
Bring to the conversation
Name the audiences, divisions or services, common sales questions, approved evidence, and person who owns the copy.
Ask to see in the scope
Ask for a page map, distinct buyer paths, content approvals, and a clear inquiry action on each relevant page.
02
Redesign an existing site
What should survive the change besides the look of the homepage?
Bring to the conversation
Bring current URLs, search and inquiry baselines, important backlinks, content owners, and the approved live-site boundary.
Ask to see in the scope
Ask for an old-to-new URL map, relevant redirects, staging noindex, launch checks, and a rollback owner before cutover.
03
Repair the inquiry path
Does a serious visitor reach the right person, with proof that the inquiry arrived?
Bring to the conversation
Show the current calls to action, form fields, routing owner, privacy requirements, and what counts as a qualified inquiry.
Ask to see in the scope
Ask for a tested submission receipt, owner routing, an error path, and agreed measurement that avoids collecting unnecessary personal data.
04
Launch and keep control
Who owns the domain, code, content, and data once the new site is running?
Bring to the conversation
Name the domain owner, editing team, accessibility needs, performance goals, and who may approve publication.
Ask to see in the scope
Ask for mobile and keyboard checks, performance evidence, documented ownership, and the boundary between hosting and optional care.
A better-looking page is not the whole brief. Decide which buyer should find it, what they need to trust, and what action makes the site valuable to the business.
01
Audience and action
Name the primary customer, the question that brought them here, and the action they should take. Different services may need distinct landing pages and inquiries.
02
Content and proof
Inventory the pages, approved imagery, evidence, and people who can approve claims. Search-friendly structure starts with useful content, not a list of keywords.
03
Ownership and change
Decide who owns the domain, code, content, analytics, and lead records; who may edit; and whether you want ongoing care after launch.
04
The launch test
Set expectations for mobile use, accessibility, speed, forms, search visibility, redirects, and a rollback path before the old site is replaced.
What gets scoped
A Website Delivery quote separates discovery, design, content, build, hosting, launch, and optional care. NEXUS Sites is a different product with its own customer-use gate.
These sources help frame the questions. They are not a LUCA certification or a promise that every control is included in a service quote.
Before you choose
Questions worth settling before you switch.
Will a new site automatically bring us more leads?
No design can promise a lead count. Start with the customers you need to reach, the questions each page must answer, and the action you want visitors to take. Agree how inquiry delivery and useful conversion events will be tested before calling the site successful.
What happens to our current URLs and search visibility during a redesign?
Inventory the existing pages and identify the new destination for each valuable URL. The launch scope should include relevant redirects, canonical and robots checks, sitemap updates, and a way to review errors after release. Search rankings may change; a redesign is not a ranking guarantee.
How do we know a contact form actually delivered an inquiry?
Test a clearly marked non-sensitive submission through the whole path: browser response, saved receipt, and the person or queue that owns the follow-up. A success message alone is not proof that the lead was stored or routed. Do not put private records into a public form test.
Who owns the website after launch?
Name domain registration, code, content, approved media, analytics access, and lead records in the written handoff. Website Delivery includes hosting; ongoing care is a separate scope decision. The agreement should explain what you can edit and how an exit or transfer would work.
Will the site meet accessibility and speed requirements?
Put the relevant accessibility criteria, devices, browsers, and performance measures in the acceptance plan. Check keyboard and mobile use as well as page-load and interaction data. A score from one lab run is not proof of accessibility or every visitor's experience.
Is Website Delivery the same as NEXUS Sites?
No. Website Delivery is a custom build-and-host service scoped with LUCA. NEXUS Sites is a separate product with its own availability and customer-use gate. Ask which path fits your need rather than assuming product access is included in a service quote.
Service here · product under NEXUS
NEXUS Sites is a separate product, scoped by request. Website Delivery is the custom build-and-host service.
