How we work
How a project runs, and what we check before a site goes live.
One studio handles the whole project: direction, design, development, verification, publication and handoff. There are four steps, and at each one you know what we're doing and what we need from you.
The process
The process
- 01
Brief
You describe the business, who it serves and what the site has to achieve, in a short form. We read it and, if we are the right studio for it, we talk.
Your partAnswer the form and a short conversation.
- 02
Proposal
We send a written proposal: what the site will contain, how it will be organised, what is included and what is not, the timeline and the price. Nothing starts until you agree to it.
Your partRead the proposal and decide.
- 03
Design and build
We set the visual direction and build the site on real content, not on placeholders. You review a working preview on a private link, with a defined round of changes.
Your partSend your materials and review the preview.
- 04
Verification and handoff
Before publishing, we verify the site: that it works on phone, tablet and desktop in every language it has, that what it says is consistent across pages, metadata and structured data, and that each point can be checked again. We publish it on your domain, check it once more live, and hand over everything: code, accounts, content, the handoff document and a dated record of what was verified.
Your partApprove the final version. From then on, it's yours.
The standard
The OwnSite standard.
Every site we make is held to the same standard, whatever its size. It isn't a separate service or an extra: it describes what we build, and what we check before anything goes live.
01
What people experience
- Performance
- Pages that load fast on an ordinary phone connection: light code, optimised images, nothing loaded that the page doesn't use.
- Accessibility
- Keyboard navigation, visible focus, sufficient contrast, labelled forms and content that respects reduced-motion settings.
- Every screen, every language
- The site works on phone, tablet and desktop, in every language it has.
- Security and robustness
- Security headers where the hosting allows them, safe external links, and forms that validate and filter spam.
02
What systems can read
A page isn't read only by people. Search engines crawl it, platforms build a preview when it's shared, and automated systems extract its facts. We build it so all of them find the same structure and the same facts.
- Semantic structure
- Headings, landmarks and markup that describe the content, so people and software read the same page.
- Search foundations
- Titles, descriptions, canonical URLs, language alternates, sitemap and structured data that matches what the page actually says.
- Sharing
- A title, description and image ready for when a link is shared, matching what the page says.
- Consistent facts
- Key facts about the project, stated consistently in the page, metadata and structured data, with no tricks aimed at any system.
- In your name
- Domain, hosting, code and accounts registered to you, not held inside our systems.
- Documented delivery
- The handoff document and the Digital Asset Folder are part of the standard, not an optional extra.
- Protected accounts
- Two-factor authentication where the service allows it, recovery notes, and the steps to close any access we held.
04
How it is verified
Before a site goes live, we check that what we built works, is consistent and can be checked again, and we record what we found.
Along with public validators and browser audits, we can use Existence Compiler, a tool that reports how clearly people, search engines and automated systems can read a site. Its report is one signal among several, never the verdict.
See a real verification record- Before publishing
- On the final version: pages, links, forms, languages, structure and the facts the site states.
- Once live
- We check it again on your domain, because the live site is what counts.
- The verification record
- What was checked, the state of each point and what was left open, dated and handed over with the site.
- What it doesn't say
- A record shows the state on one date. It isn't a certificate, and it doesn't guarantee how the site or any search engine will behave later.
Promises
What we promise, and what we won't.
- We promise a site built to this standard.And you receive the record of how it was checked.
- We don't promise rankings, traffic or sales.Nobody controls those. A well-built site is the honest starting point, not a guarantee.
- We don't promise inclusion in AI search.We make the facts clear and consistent so they can be read correctly. What those systems show is up to them.
When you're ready: a short form, no payment, no commitment.
Start a project