One team draws the layout and writes the code, so the site you approve is the site that ships.
Pick the closest fit. The exact scope gets settled in the first conversation, not on this page.
Home, services, about, contact, and whatever else your customers look for. We plan the page structure with you, design it, and build it.
good fit when: the site has to represent the whole company.
One page, or a small handful, built for a single goal: launching a product, running a campaign, collecting sign-ups. Because the scope is small, it ships sooner.
good fit when: you have one launch, one campaign, one thing to say.
We review the current site, keep what works, and rebuild the rest. Old URLs are redirected to their new pages, so existing links and search rankings survive the move.
good fit when: you have a site, and it is dated, slow, or hard to edit.
Content changes, new pages, updated dependencies and the occasional broken thing, handled after the site is live, monthly or as requests come in.
good fit when: you would rather not run updates and fixes yourself.
Four stages, in order. Nothing starts until the one before it is done.
We start with a conversation about your company, your customers, and what the site has to do. Then we agree on the pages, what each one is for, and which content already exists.
you get: a written scope listing what will be built and what will not.
We design the key pages and settle typography, color and layout. You review, we revise. Approved decisions are written into the code as shared styles, so the built site matches the drawn one.
you get: layouts for the main pages, plus the style rules the code will use.
The front end is written by hand in HTML, CSS and JavaScript, with a framework only when the project needs one. We check every page on real phones, at different screen sizes, and with a keyboard alone.
you get: a private staging link to click through before anything is public.
We connect your domain, set up hosting, and deploy. Then we hand everything over and walk your team through it.
you get: the live site, the source code, the logins, and a README.
$ tree client-siteclient-site/|-- src/| |-- pages/| |-- components/| `-- styles/| `-- tokens.css colors, type, spacing|-- content/ text and images your team edits|-- README.md run it, change it, deploy it`-- DEPLOY.md hosting and domain notes$ We pick the smallest tool that does the job. A five-page company site rarely needs a framework.
Anything not answered here, ask in the form below.
It depends on the number of pages and the features you need. You get a quote in writing, with the scope, before any work starts.
It depends on the scope. The written scope from the brief includes a schedule you can plan around.
Not all of it. In the brief we agree what already exists and what still has to be written.
Yes, if you want that. We set up a CMS so your team can change text and images without touching code.
You do. At launch the source code goes into a repository you own.
A few lines is enough. What the company does, what is wrong with the current site or why there is none, and any date you are working toward.