Websites, redesigns and landing pages that bring your brand and business goals together. Clear journeys, thoughtful design and a maintainable build.
A visitor decides whether to keep reading before they scroll. That decision is made by a headline and one image.
Illustration, not a live result.
Six parts of the same project. Design, content and code decide each other, so they are planned together rather than handed down a line.
The journeys the site has to support, the pages that serve them, and a structure that lets someone find their own way through.
A visual language built as reusable components, so the site still looks right after your team has added fifty pages to it.
Front-end build, CMS setup and the integrations behind your forms, so editing a page never has to wait for a developer.
Page copy, structure and the technical SEO decisions that are far cheaper to get right before launch than to repair after it.
Core Web Vitals, responsive behaviour and accessible markup, treated as build requirements rather than a post-launch cleanup.
Tracking verified before go-live, a documented handover, and a clear agreement about who maintains what afterwards.
Design is the way a website works, reads and feels — from the first impression to the next useful action.
Three ways a connected strategy could change the picture.Concept projects · Fictional brands and illustrative results.
ECOMMERCE / Form & Field
A search-led growth concept for a homeware brand. Connecting useful content, product discovery and a simpler path to purchase.
Illustrative results
B2B SOFTWARE / Northline
A connected paid-media concept for a software business. Sharper audience targeting, clearer landing pages and measurement from first click to qualified lead.
Illustrative results
MOBILE APPS / Dailyform
An app-store growth concept that brings everyday value into focus. New positioning, localized creative and a store page designed to turn interest into installs.
Illustrative results
From the first sketchDesigners and developers work through the same questions together. Your content, business requirements and the way the site will be maintained stay in the room.
The same six questions, answered three different ways.
| Area | With 1nstat | A typical agency | In-house, alone |
|---|---|---|---|
| Strategy | One goal the whole site serves | A page-count deliverable | Clear intent, no capacity |
| Design | A component system, not just pages | A set of mockups | Depends on available hours |
| Content | Planned alongside the design | Your job, at the end | The thing that stalls it |
| Search | Protected through the migration | Handled afterwards, if at all | Hoped for |
| Launch | Tracking verified, handover documented | Files delivered | Whoever built it remembers |
| Working with you | A named lead, open reasoning | An account manager in between | Full context, no hours |
Site size, CMS, the state of your content and how much your team will maintain decide the shape. This is in every engagement.
A focused landing page can be weeks. A full site with new content is usually a few months, and the variable is almost always content rather than design or code. We give you a sequence with dates once we know the page count and who is writing.
Either. If you have a brand, we extend it into a system the site can be built from. If you don’t, the visual language can be developed as part of the project — and we say up front which one the estimate assumes.
Whatever suits the team maintaining it. We would rather use something your editors already understand than something we prefer. If the site genuinely needs a custom build, we explain the trade-off before you commit to it.
That is the plan, and it takes work. We audit the current URLs, structure and content, carry over what earns traffic, and map the redirects before the first page moves. Some movement after a migration is normal; losing the traffic is not.
Yes. That is a build requirement, not a bonus. Pages are assembled from components your editors can rearrange, and we document how before we hand over.
Often that is the better project. A focused rebuild of the pages that carry the decisions costs less, ships sooner and is far easier to judge than replacing everything at once.
Someone who can make decisions, access to whatever exists now, and an honest answer about who is writing the content. That last one decides the timeline more than anything else in the project.
We can, or we can hand it over properly so someone else does. Either way, launch includes documentation and a written agreement about who owns what.
You do. The designs, the code, the content and every account stay yours, and we hand over the documentation and the reasoning behind it.
LET’S MAKE THE NEXT MOVE.
Tell us where you want to go. We’ll help you find the right way forward.
Share your goals and the challenge in front of you. We’ll review your brief and get back to you about how we can help.
