Services

Digital work that holds up after launch.

I work across websites, accessibility, frontend engineering and practical AI systems. The shape of the engagement follows the problem — not a fixed agency package.

Engagements are scoped around the problem, not the discipline.

Tell me what you need to achieve

End to end

From problem to production.

I can help diagnose one part of a digital problem, improve something that already exists, or take the work through design, implementation, testing and launch.

Engagements

Ways to work together

You don’t need to know which discipline you need before we talk. Start with the problem.

Fix something

Something already exists, but it isn’t working as well as it should. That might mean accessibility, search, performance, usability, content, implementation — or a mix of them.

Build something

You need a new website, digital experience, workflow or AI-enabled system, with the thinking and implementation connected from the start.

Figure something out

You know something isn’t working, but you’re not yet sure what the right solution is. We can define the problem before deciding what to make.

Work alongside the team

You need an extra pair of multidisciplinary hands for a period of time — helping the team move through design, code, accessibility, search or AI without creating another silo.

Websites

For businesses whose website no longer explains what they do or helps people take the next step.

Start with

Your business, your audience, the current site if there is one, and what needs to change. A new website and a rebuild start with the same question: what should this site help people do?

What I do

I shape the content and page structure, design and implement the responsive frontend, and connect a CMS where it is useful. Accessibility, technical SEO fundamentals and testing are part of the work, with Production deployment and later refinement agreed within scope.

What you receive

Depending on scope: an implemented website or a focused improvement to the existing one, tested changes, editable content where a CMS is included, and handover notes for maintaining what was built.

See the website work: Anders Norrman →

Accessibility

For website owners and product teams that need to understand barriers and get them fixed.

Start with

An explicit scope: the pages, components and interactions to test, the relevant WCAG criteria, and the evidence needed to review the result.

What I do

Test. Investigate. Fix. Retest. I combine automated checks with manual investigation of keyboard behaviour, focus, semantics, accessible names, contrast and responsive reflow. I implement fixes where agreed, or support your team through remediation, then retest the changed behaviour.

What you receive

Depending on scope: findings and recommendations, implemented fixes or remediation guidance, and a record of what was tested, what passed on retest and what remains unresolved. Evidence stays tied to the agreed scope.

Automated tooling is part of the process, not the whole process. Zero automated violations does not mean universal accessibility. Findings describe what was actually tested; this is not certification or a blanket WCAG-conformance claim.

See tested accessibility work: Anders Norrman →

Practical AI systems

For people and teams whose internal workflows need dependable context, useful automation and clear human decisions.

Start with

The work you are trying to do, the information it depends on, and the points where an error or an unchecked action would matter. We identify whether AI is useful and where ordinary software is enough.

What I do

I design and build internal workflows that connect AI, knowledge and software. That may mean an agent with bounded tasks, a shared-context system, or an operation with a human review gate. Prompt and context design sit alongside integration, testing and explicit permission boundaries. AI handles semantic reasoning where it adds value; deterministic software handles deterministic work.

What you receive

Depending on scope: an implemented workflow or bounded system change, documented context and permission boundaries, tests and execution evidence, and handover context for operating or refining it. Human review stays where judgement matters.

I use AI heavily, but I don’t sell magic. Gabi OS is real internal-product proof, not an off-the-shelf client product. Its v1 architecture and implementation reached verified acceptance; it remains under active development and not every component is deployed or live.

See the internal AI system: Gabi OS →

Frontend / product engineering

For product teams with an existing design or codebase that need implementation, remediation or better frontend quality.

Start with

Your current designs, components and code, the behaviour that needs to change, and how your team reviews and releases work. I join the existing project with a bounded scope rather than treating it as a new website.

What I do

I implement interfaces from existing designs, refine components and design-system patterns, and investigate frontend defects. React, Next.js and TypeScript are tools for making the agreed behaviour work: responsive layouts, accessibility, integrations with existing systems and tests belong in the implementation.

What you receive

Depending on scope: implemented and reviewed code, component or interaction fixes, tested changes, and notes that explain the decisions and remaining limits so your team can continue the work.

See product engineering in Gabi OS →

Collaboration

I work with you, not around you.

The goal isn’t to disappear with a brief and return with a mysterious deliverable. I want to understand the context, make decisions visibly, and leave behind something your team can actually use and maintain.

How it starts

Agree the scope before the work starts.

Tell me what you want to achieve or fix. A current site, a product problem or a workflow that keeps breaking is enough to start. You do not need a finished brief.
I look at what is there. We identify the smallest useful scope and what access or context the work needs.
We agree what success looks like. That includes what I will do, what is outside scope and how we will review the evidence.
I work against that scope. If a new finding changes the work, we discuss it rather than quietly expanding the engagement.
We review the result. The agreed work is tested or reviewed before it is called done, with remaining limits made clear.

Have a problem in mind?

Tell me what needs to work better.

Whether it is a business website, a product interface, an accessibility issue or an internal AI workflow, start with the current problem. We can work out the scope together.

Start a conversation