Intactic

Capability

Sites and portals that carry the brand.

Marketing sites, customer portals and internal dashboards where design quality and load time are part of the product, not a coat of paint applied at the end.

Typical engagementPlatform build
Team2–4 people
First phaseDesign direction, 2 weeks

The problem

A website is judged in the first second.

On a phone, on a train, before a single word is read. Everything after that judgement, from the pricing table to the login form, is read in the shadow of how the page felt when it loaded.

Most corporate sites fail in the same three places: a design system that exists only in a file, content the marketing team cannot edit without a ticket, and a page weight nobody measured.

System map
CMS
Portal
Sign-in
Search
CoreDesign system
Analytics
Media
Forms
Delivery
Design system at the centreweb-platforms

Deliverables

What we build.

Six pieces of work, scoped in discovery and delivered in two-week increments.

Design system

Tokens, components and rules your team can extend without breaking the brand.

Marketing site and CMS

Structured content, previews, and publishing that does not require a developer.

Customer and partner portals

Authentication, roles, documents and account history in one place.

Performance

Budgets per page, set before design and measured after launch on real devices.

Accessibility

WCAG 2.2 AA, tested with a keyboard and a screen reader, not only a checklist.

Analytics and consent

Events that answer real questions, and a consent model that holds up to review.

Approach

How we work on it.

Three working rules that shape the build, and the stack we usually reach for.

Design in the browser

Layouts are proven at 360, 768 and 1440 pixels before they are approved, not after.

Content is a system

Fields, not free-text boxes. Editors get guardrails; readers get consistency.

Measure before launch

A desktop score is a starting point. Real devices on real networks decide whether it ships.

Typical stack

HTML / CSS / TSNext.jsAstroSanityCloudflare

Static where it can be, dynamic where it must be. Most of the site should be a file on a CDN, not a database query.

How it starts

A two-week design direction: type, colour, grid and two page templates built in the browser for review on real devices.

Scope this work

Related

Usually built alongside.

Most engagements combine two or three capabilities; these are the pairs we see most.

Next step

Tell us what you’re building.

Send a short brief. You get the questions that matter, a rough shape of the work and a straight answer on fit.