The full process
Nine steps from the free read to training and handoff, and what you get at each one.
Websites
A custom website your company owns, kept current by your own people.
We build the site around how your business takes in work, like quote requests with the drawings attached, service and maintenance requests, and the catalogs and certifications buyers look for. The domain, the hosting account, and the code are yours from the start, and we train your people to keep it current before handoff. It’s optional and never required before AI work, and if you do both, the same people on your team usually run the site and the AI work.
- Service
- Optional, never required first
- Starts with
- A free written read
- Ownership
- Yours from the start
- Kept current by
- Your own people
Ownership and control
You own the site and everything it runs on
Your company holds every account, and the handoff isn’t finished until the site publishes from them without us.
Your domain and hosting account
Both are in your company’s name, and your people hold the admin and billing control. We work through access you grant us and never ask for your passwords.
Your repository and code
The site’s code lives in your company’s GitHub organization from the first day, so the code, the content, and the record of every change belong to you.
Your decisions
You decide what changes, when, and who works on it. There’s nothing to pay us each month to keep the site running, and after the handoff we remove our access to publish.
Custom to the business
Built around how your business takes in work
Every site is custom. We start with the requests that come in, the documents buyers ask for, and where that information needs to go next, and you decide which pieces are worth building. Each one is scoped in the build.
01
Quote requests with the drawings attached
An RFQ form can ask for what your estimator needs to start, like drawings, quantities, materials, and the due date, so the request arrives ready to quote and goes to the person who quotes it.
02
Service and maintenance requests
Customers, or your own people, can send a service or maintenance request with the equipment, the location, and photos, and it goes to whoever schedules that work. Job applications can reach whoever is hiring the same way.
03
Catalogs, spec sheets, and certifications
Your parts, products, or capabilities can sit in a catalog with the spec sheets, certifications, and line cards beside them, so your sales team sends the same link a buyer finds on their own.
04
Forms that feed the next step
What a form collects can be shaped for where it goes next: a shared inbox, a chat channel, your CRM, your quoting or scheduling process, or a maintenance queue. We shape what the form collects so a system you add later can take it in.
05
Pages written for buyers and for search
We research and write pages around the questions buyers ask before they call, and you confirm every company fact. Each page carries search markup, and the site publishes sitemaps and an llms.txt file, a proposed format written for AI tools. Search engines decide what to rank, so we don’t promise rankings.
06
Tools built into the site
Some businesses need the site to do more, like a customer login for order documents and certifications, a searchable catalog, a scheduling tool, or an internal board where your team sees every incoming request and who has it. Each of those is a bigger job, so we scope it once we understand the work it supports.
Part of the business
Your Champions keep the site current
One or two people on your team keep the site current. We call them Champions, and they’re usually the same people who own your AI work. When you add a capability, earn a certification, or change your hours, the person handling that change updates the site as part of it.
Step 1
Ask in plain English
Your Champion tells an AI assistant what should change, like new hours, a new certification, or a page for a new capability.
Step 2
The assistant reads the site’s instructions
Before it touches anything, it reads which template each kind of page uses, where the company facts live, and the written steps for adding a page.
Step 3
Checks run before anything publishes
Automatic checks run on every build. A page missing its search markup doesn’t publish, and the check says what’s missing.
Step 4
A person reads it and publishes
Someone on your team reads the change before it goes live. A bigger change can go to a private preview link first.
The site’s company facts work like a small Operating Standard. A fact is written down once, after someone confirms it, and pages and search markup pull from that one file, so the site says the same thing everywhere. Small text edits also work in GitHub’s web editor, with no assistant involved.
The site you’re reading runs the same way. Its repository carries instructions an AI assistant follows, and its build stops when a page is missing its search markup.
Training and handoff
We train your people before we hand it over
Before handoff we train your Champion on your own site: how to describe a change to an AI assistant, how to make a small edit in GitHub’s web editor, and what the checks are saying when a page won’t publish. The handoff is done when one of your people has made a real change to the site on their own, start to finish.
If you later want something new built, like a customer login or a connection to a new system, that’s a new project, scoped and quoted on its own. Everyday changes stay with your people, and we don’t take on ongoing website maintenance.
How a build goes
From the free read to a trained handoff
OP 010
Free written read
You getA read you can check yourself
We go through the site on a desktop and a phone and put a date on every finding.
OP 020
Conversation and scope
You getA written scope and quote
We talk through what the site should take in and hold, then you approve the pages, the content plan, and any functionality.
OP 030
Build in your accounts
You getRevisions before launch
We build in your repository and hosting account, and you review the working site at a private link while the current one stays up.
OP 040
Launch, training, and handoff
You getA documented handoff
We test redirects and forms on the live domain and train your Champion until they’ve made a real change themselves.
Pricing
Every build is scoped and quoted in writing
There’s no package and no published price. A focused rebuild and a site that takes quote requests into your quoting process are different jobs, so the quote comes after the free read and a conversation.
The approved sitemap and content plan, plus any functionality we agree to build, set the scope, and there’s no page cap. Each build is quoted in writing against that plan. Whatever the scope, every build includes these:
- Research-backed pages for your services, industries, products, and standards, with every company fact confirmed by you
- Forms built around what the next step needs, plus migration with redirects, search markup, sitemaps, and an llms.txt file
- A private preview, the revision rounds set in the quote, and training for the people who will keep the site current
Next to the AI work
A website isn’t required before AI work
A website build has its own scope, and you can start with your systems and leave the site as it is.
During a build we send a short What We Noticed note about process opportunities we could see in your content and our conversations. It’s not the plan an Opportunity Assessment produces, because a plan for AI work takes time on site with your people and is scoped separately. If something in the note interests you, the next step is the same free conversation anyone can start.
Go deeper
Before you decide
Website FAQ
Who owns what, how your people keep the site current, what a site can do, and how a build is scoped.
Send us your website address.
We’ll send back a dated, written read of what the site does well, where buyers get stuck, and what we’d change.
Conversations are always free.