Building for the web since 2008

Malmö · Remote worldwide

We build the software serious companies run on.

Seventeen years building for the web, nine of them inside companies like Meta and IKEA. Platforms, integrations, storefronts and mobile apps — designed with restraint, built to outlive the people who commissioned them.

Our engineers have built software at

  • Meta
  • IKEA
  • Consid

and other product teams across Sweden and abroad

Who we are

Most software is built by people who have never had to live with it. We have — since 2008, and lately inside Meta and IKEA. That is the whole difference: every decision here is made by someone who will still be answering for it in three years’ time.

17Years building for the web, since 2008
9Of them inside companies like Meta and IKEA
2Large builds at a time, on purpose
100Lighthouse on every front-end we ship

What we do

Five ways we get involved, and one standard of work.

01

Web apps & platforms

The systems your business runs on. Cloud-native services, multi-tenant SaaS, CRMs, internal tools, billing and the unglamorous plumbing underneath — built the way we built a telecom CRM from an empty repository.

  • Architecture & technical due diligence
  • Node.js, TypeScript, NestJS, Next.js
  • Microservices, API gateways, event-driven messaging
  • PostgreSQL, MySQL, MongoDB
More on web apps & platforms
02

Integrations & APIs

Making systems that were never designed to talk to each other behave as one. CRM syncs, payment rails, third-party APIs and the data compliance obligations that come attached.

  • CRM & SaaS integrations (Pipedrive, Upsales, Zoho)
  • Payment and transaction layers
  • REST, RPC and GraphQL against awkward APIs
  • GDPR-compliant data workflows
More on integrations & apis
03

Marketing sites & commerce

Sites that carry a brand properly and convert without begging. Design-led front-ends built with the designer rather than from a handoff, and storefronts that survive a campaign spike.

  • Design-led builds, bespoke CSS — no bought themes
  • Next.js, headless CMS your team can use
  • E-commerce and Magento experience
  • Core Web Vitals as a hard requirement
More on marketing sites & commerce
04

Mobile apps

iOS and Android from one codebase where that's the right call. We have taken our own app through App Store review, so we know exactly what the last ten percent costs.

  • React Native, one codebase, both stores
  • In-app purchases & virtual currency
  • App Store / Play release pipelines
  • Auth, SSO and offline-tolerant data
More on mobile apps
05

Technical partnership

A senior engineering brain on retainer. For founders without a CTO, teams that have stalled, and projects that need rescuing before they need rebuilding.

  • Fractional CTO & architecture review
  • DevOps: Terraform, Docker, Kubernetes, CI/CD
  • Rescuing stalled or inherited codebases
  • Team augmentation & mentoring
More on technical partnership

Not sure which of these you need? That’s a normal place to start.

Technologies we work in: TypeScript, Node.js, React, Next.js, NestJS, React Native, PostgreSQL, MySQL, MongoDB, GCP, AWS, Terraform, Docker, Kubernetes, GraphQL, GitHub Actions.

How we work

No discovery theatre. No surprise invoices.

Every phase is scoped, priced and deployable on its own. You can stop after any of them and still own something that works.

011 week

Orientation

A paid, fixed-scope discovery week. We map the domain, the constraints and the real business goal, then hand you a written technical plan with costs attached. You own it whether or not we build it.

022–4 weeks

Design

Interface and system design in parallel. Real content, real data shapes, real edge cases — no lorem ipsum, no screens that can't be built. You see the product before a line of feature code is written.

036–16 weeks

Build

Two-week increments against a public board. Every increment ends on a deployed environment you can click through. No status meetings that could have been a changelog.

04Ongoing

Launch & after

Performance budgets, accessibility audit, monitoring and a documented handover. Then a maintenance retainer, or a clean exit with your team fully in control. Both are fine by us.

How we're this fast

AI makes us fast. Meta and IKEA taught us to make it safe.

We use AI heavily, and we're not coy about it — it's most of the reason a build that used to take nine months takes four, and costs accordingly. What hasn't changed is the review discipline, learned somewhere it is the cost of entry rather than a nice-to-have, or who is accountable for every line.

FasterWeeks, not quarters, between a decision and a deployed increment.
CheaperThe leverage shows up in the quote, not just in our margin.
CorrectTested, reviewed and secured to the standard the work demands, however it was written.
01

A senior reads everything

Nothing reaches your repository unreviewed by a person who could have written it themselves. AI writes the first draft; the judgement about whether it's the right draft is not delegated.

02

Tests are the contract

Generated code is guilty until proven correct. Behaviour is pinned by tests written against the requirement, not against the implementation — so a plausible-looking wrong answer fails loudly instead of shipping quietly.

03

Security reviewed deliberately

Authorisation, input handling, secrets and dependencies get explicit human review, plus automated scanning in CI. The failure modes of AI-written code are well known by now, and we check for them by name.

04

We can explain every line

If nobody on the team can explain why a piece of code exists, it doesn't ship. That rule is what keeps a codebase maintainable, and it's the one most AI-assisted work quietly abandons.

Why us

You have three other options. Here’s how we compare.

01

Instead of an agency

No account manager between you and the work, no junior learning on your budget, and no markup on subcontractors you never meet. The person on the first call is the person writing the code — and the overhead you are not paying for shows up in the quote.

02

Instead of a freelancer

Production experience from inside Meta and IKEA, not just a portfolio of launches. Infrastructure, CI/CD, testing and security handled as standard rather than as extras — and a studio that still exists when one person is ill.

03

Instead of hiring

No three-month recruitment, no salary plus social fees plus equipment plus onboarding before a line ships. Senior capability from week one, at a cost you can stop — and if you do go on to hire, we hand over cleanly and document as we go.

Fixed price per phase

Quoted after discovery, so you are never signing an open-ended hourly commitment.

You own everything

Your repository, your accounts, your infrastructure — outright, from the first commit.

Stop whenever

Phase-to-phase contracts with 30 days' notice. You keep everything built, deployed and documented.

An honest no

If we're not right for the project you'll know within a working day, usually with a better suggestion attached.

Still reading? That usually means it’s worth a call.

Questions

Anything not answered here, ask directly — hej@swoo.se

What does a project cost?

Small, fixed-scope work starts at €1,000 — an integration, a landing page, a performance or security rescue. A discovery week is €2,500. Most full builds land between €15,000 and €80,000 depending on scope, quoted at a fixed price per phase once discovery is done, so you never sign a blank cheque. Retainers start at €1,500/month. Those numbers are well below what this work cost three years ago, for the reason set out below — we work faster now, and we price the work rather than the hours.

How quickly can you start?

Small fixed-scope work can often start the same week. Discovery usually begins within two weeks, and full build slots are typically booked four to six weeks out — we deliberately keep no more than two large builds running at once, though smaller work fits alongside them.

Is there a minimum project size?

€1,000. Below that the conversation costs more than the work. Above it we're genuinely happy to take on small, well-defined jobs — a slow site made fast, an integration that keeps breaking, a security issue you'd rather not sit on. Small work is how most of our long engagements started.

Do you work with existing teams and codebases?

Often. Roughly a third of our work is joining an in-house team, or taking over a codebase someone else left behind. We'll tell you honestly whether it's worth saving.

Do you use AI to write our code?

Yes, and we'd be suspicious of anyone in 2026 who says otherwise. It's a large part of why we're quicker and cheaper than a comparable team. Every line still passes senior review, tests written against the requirement, and explicit security review before it reaches your repository — and we can explain any of it on request. You're buying the judgement, not the typing.

Who actually does the work?

Senior engineers only, and the person you talk to in the first call is the person writing your code. Nothing is offshored, and nothing is handed to a junior to learn on.

Who owns the code?

You do — outright, from the first commit, in your own repository. No licensing games, no proprietary platform you can't leave.

What if we need to stop?

Contracts run phase to phase with 30 days' notice. You keep everything built to that point, deployed and documented.

Where we work

A development studio in Malmö, working across the Öresund region and remotely.

Malmö & Öresund

We are based in Malmö and work in person with clients across Skåne — Malmö, Lund, Helsingborg and Copenhagen are all a short trip. We work in Swedish and English, so procurement, contracts and standups can all happen in whichever your team prefers.

Remote, properly

Most of our work is remote and has been for years, including engagements with distributed teams at global companies. Written decisions, deployed increments and a public board beat a calendar full of check-ins — wherever your team happens to sit.

What we’re usually hired for

Web application development, system integrations and API work, e-commerce and headless CMS builds, React Native app development, cloud infrastructure on GCP and AWS, and fractional CTO or architecture support for teams without a senior engineer in the room.

Let’s build something that lasts.

Tell us about the project. If we’re not the right studio for it, we’ll say so — and usually point you at someone who is.