B2B website design and development: the site does the explaining.
Design and build for companies whose buyers do most of the research before anyone picks up the phone. The code, the hosting and the domain are yours from the first commit.
● Start here
Tell us about the business.
It takes about a minute. It reaches the people who would do the work rather than a sales inbox, and if we are not the right fit for what you need we will say so.
Goes to hello@katama.io. No sequences, no newsletter, no list.
● Design and development versus conversion work
Website design and development builds the site. Conversion work improves the one you already have.
If the structure is sound and the pages simply underperform, you want the second and it costs far less. If every page argues for the company rather than the buyer, and nothing can be changed without a developer, testing will not save it.
The site is the only rep always on duty.
Most of a B2B purchase happens before anyone talks to you. The site is what does the explaining in the meantime, and on most sites it explains the company rather than the problem the visitor arrived with.
So the pages describe the team, the values and the founding story, and the visitor leaves without learning whether the thing solves their problem. Design gets blamed for it. The structure and the copy were the fault.
The second failure is operational. The site ships, marketing needs a page changed, and the change needs a developer who is busy with something else. Six months later nothing has been updated and the site is quietly out of date.
A site marketing cannot edit is a site that stops being true. We build for the people who will maintain it, which usually means fewer bespoke one-off pages and more blocks your team can assemble without asking anyone.
What we build.
Design and development are two different jobs and this covers both. Design settles how the site is structured, what each page has to prove and what it looks like. Development turns that into something fast, accessible, and editable by the people who will maintain it.
They run as one project because separating them is where sites go wrong: a design nobody can build, or a build nobody designed. Strategy, structure, design, build, in that order, and the wireframes come from what a page has to prove rather than from a template picked first and filled in afterwards.
Performance and accessibility are constraints on the build, not an optimization pass bolted on at the end. A page that takes four seconds to render has already lost the visitor it was built for.
Everything lands in your accounts. Repository, hosting, domain and analytics are yours from the first commit, there is no license to renew, and nothing we build stops working if you stop working with us.
● The design half
- Audit, discovery and information architecture
- Sitemap and page structure
- Wireframes
- Visual design and art direction
- Design system and component library
- Responsive design down to phone widths
The build half
- Front end build
- CMS setup your team can actually use
- Performance and core web vitals
- Accessibility and technical SEO
- Analytics and conversion tracking
- Migration, redirect mapping and handover
How the work runs.
Audit what exists
Which pages earn traffic, which ones convert, and what breaks if they move. The redirect map starts here, because losing rankings to a relaunch is the most common way this goes wrong.
Structure before surface
Information architecture and page structure signed off before anything is designed. Arguing about colour while the navigation is still unsettled wastes everybody’s time.
Design and build
A design system rather than a stack of one-off pages, with templates that cover what you will need next year as well as what you need at launch.
Migrate and hand over
Redirects in place, tracking verified against real sessions, and your team trained on the CMS before launch rather than a month after it.
What we report.
A relaunch that looks better and performs worse is a failure with good photography. These are the numbers that decide it.
Conversion rate
By page and by template, measured against what the old site did. The number the whole project exists for.
Speed and accessibility
Core web vitals and accessibility checks run on real pages after launch, reported rather than asserted in a proposal.
Rankings held through migration
Tracked either side of the move. A relaunch that loses organic traffic has not succeeded, however good it looks.
Who this suits.
- Your buyers research long before they contact you
- Marketing needs to edit pages without a developer
- The current site cannot support the pages you need
- You want to own everything that gets built
- The structure is sound and only the pages underperform
- It has to be live in three weeks
- Nobody can sign off structure before design starts
- You want a bought template filled in as cheaply as possible
Fair questions.
Do you redesign, or start from scratch?
Whichever the audit argues for. A site with sound information architecture and a tired visual layer is a redesign. A site where every page fights the buyer is a rebuild. We tell you which one you have before quoting, and the answer is a redesign more often than agencies admit.
Can we buy just the design, or just the build?
Usually not, and the reason is not commercial. A design handed to somebody else’s developers loses half its decisions in translation, and building from a design we did not draw means inheriting choices we cannot explain to you. If you have a design team already, or developers sitting idle, say so early and we will tell you honestly whether splitting it is worth it.
What do you build it on?
Usually a headless or static setup your team can edit without filing a ticket, chosen to fit the people who will actually maintain it. We do not have one platform we sell to everybody. If your team lives in a CMS that already works, keeping it is a legitimate answer.
Who owns the site when we are done?
You do. Repository, hosting, domain, analytics, all of it in your accounts and in your name from the first day. There is no license to renew and nothing that stops working if you stop paying us.
Can you work with our brand guidelines?
Yes, and we prefer to. If the guidelines exist and are good, we build to them. If they do not exist, or they were made for a deck rather than a screen, we will tell you what is missing and either fill the gap or point you at brand and messaging first.