Website
For visitors. Pages, articles and forms, found in search and edited by your team.
We build your approved design into a site your team can run: templates, a CMS they edit themselves, fast pages and forms, plus CRM and migration when you need them.
Each page type, built once.
Fields, previews, editor roles.
Sized for phones, lab-tested.
Clean URLs, metadata, sitemap.
Inquiries reach your CRM or inbox.
Each old address mapped before launch.
We agree the content types and their fields with the people who will edit them: titles, summaries, images, authors.
Content modelFields fill a template, so a short or a long title, an image or none, still reads as the design intended.
Templates tested with real contentEditors check a draft in preview and publish it when it is ready. A new article needs no developer.
Roles, previews and an editor guide| Old address | Answer | New address |
|---|---|---|
| /solutions/payroll-software | 301Moved | /products/payroll |
| /blog/2019/year-end-checklist | 301Moved | /guides/year-end-checklist |
| /company/about-us | 301Moved | /about |
| /webinars/spring-2020-launch | 410Removed | No replacement |
| /pricing | 200Kept | /pricing |
Checked again on the live site
A permanent redirect, straight to the page that replaces it.
A 404 or 410 when nothing replaces it, not a redirect to the home page.
The page keeps its address, so no redirect is needed.
Five steps, with a preview link from the first template. You approve the site before anything goes live.
Start from the design
We go through the designs, the content you have and the pages you plan to add, and list what the mockups leave open: states, screen sizes, long content and who edits what.
We agree with you
Whether we build the whole site or one part first.
You receive
Before the build
We agree which templates, integrations and content moves the first release includes, and the CMS that suits your team, on hosting you choose.
We agree with you
What the first release includes and leaves out, and the CMS it runs on.
You receive
On a preview link
Templates are built section by section on one set of design tokens, then connected to the CMS, so your editors try real content while the build is in progress. Every change is reviewed by a second senior engineer.
We agree with you
Each template on the preview link, with your real content in it.
You receive
Before launch
Forms, CRM, analytics and redirects are connected and tested. Every template is checked on desktop, tablet and phone, with a keyboard, and against the speed and search basics.
We agree with you
The pre-launch checklist and the redirect map.
You receive
Launch day and after
We launch, check redirects, forms and analytics on the live site, and hand over guides for editors and developers. For 30 days after handover, we fix bugs within the delivered, agreed scope at no extra cost.
We agree with you
The launch date, then the handover to your team.
You receive
For visitors. Pages, articles and forms, found in search and edited by your team.
For people who sign in. Accounts, data and workflows, changed in planned releases.
Web app developmentMany products need both. They can share one design system.
It depends on the number of templates, the content and addresses that move over, the CMS and editing setup, the integrations and any motion or interactive parts. After a first conversation we outline the work, timing and budget, and we agree a fixed price for a clear scope before the build starts. You approve the cost of any additional work before it starts.
It depends on the number of templates, the integrations and how much content moves over, so we agree the timeline together with the scope. You follow progress on a preview link and can try each template with real content as soon as it is ready.
Yes. We review your design files first and list what they leave open, such as hover and error states, phone layouts or very long content, then agree how to handle each point before building. If the site still needs designing, we can do the design and the build as one project.
We choose it with you when we agree the scope: who edits the site, what they publish, how many languages it has, which previews and roles your team needs, and what it should cost to run. Field names, previews and roles depend on the CMS you choose, and we set them up around your content.
Yes. We model your content types and fields with the people who will edit them, set up roles and previews, and hand over a short editor guide. Editors change text, images and whole pages within the templates, so the layout holds long and short content and each page keeps its search fields.
We plan the move to carry over what works. Every old address gets a decision before launch: it stays as it is, redirects permanently to its replacement, or returns a 404 or 410 if the page is removed without one. Titles and descriptions move with their pages, and we test the redirects again on the live site. Rankings can fluctuate for a while as search engines recrawl the site. If the structure and design also need rethinking, see website redesign.
Yes. Templates use headings in order, labeled form fields, visible focus states and readable color contrast, and every template is checked with a keyboard before launch. Motion follows the visitor's reduced-motion setting. If your organization has to meet a specific accessibility standard, we name it in the scope and check against it.
You own the code and design files, with access from day one and documentation to support future development. For 30 days after handover, we fix bugs within the delivered, agreed scope at no extra cost. Ongoing support or new templates can be arranged.