Web development,built to stay fast.

Marketing sites and web apps on a typed stack, shipped to a staging link every Friday and handed over clean.

Our usual stack

  • Next.js
  • Nuxt
  • TypeScript
  • Node
  • Postgres
  • Sanity
  • Vercel
  • Playwright

Most rebuilds fail the same way.We plan for it on day one.

Four ways a web build usually goes wrong, and what we do from week one so it does not.

  1. The site looks right in the demo and crawls on a phone.

    A performance budget is set in week one and checked on every Friday build.

  2. Marketing waits on an engineer for every copy change.

    A CMS with page blocks we design together. Your team publishes alone.

  3. The agency leaves and nobody can read the code.

    Typed code, tests and docs in your own GitHub from the first commit.

  4. Launch day turns into a weekend of fixes.

    Staging mirrors production, so launch is a switch you sign off on a Tuesday.

What you get at handover.All of it in your accounts.

  • Engineer checking a web page on a row of phones and a laptop in the device lab

    Tested on the devices your users have

    Every page checked on real iPhones, Androids and laptops in our device lab, plus Safari, Chrome and Firefox.

    • github.com/vonmo/sitemaintests passing214docs/handover.mdupdated Fri

      A production codebase

      Typed, tested and documented, in a GitHub organisation you own from the first commit.

    • vonmo.comLive

      Launch and 30 days of support

      We switch DNS with you on the line, then watch errors and speed for a month.

      • Hero
      • Logo row
      • Pricing table
      • Feature grid
      • FAQ
      • Blog post

      A CMS your team runs

      Pages built from blocks we design with you. New pages ship without a ticket.

      • Redirects from every old URL
      • Sitemap, meta and Open Graph
      • Privacy-friendly analytics

      SEO and analytics, done

      Old rankings carried over, events in place for every signup and demo request.

A typical build

Ten weeks from kickoff to live.A staging link every Friday.

How we ran the new Vonmo site and customer portal. Your proposal comes with a plan like this, week by week.

  1. Week 2Prototype signed offYou approve every key screen before we write production code.
  2. Week 5Midpoint reviewHalf the pages live on staging. We re-check scope and budget together.
  3. Week 9Launch sign-offContent in, every page tested. You give the go for launch week.
  4. Week 10vonmo.com is liveDNS switched on a Tuesday morning. Code, docs and logins handed over.

Web build questions.Straight answers.

What founders ask Tomás before a web build.

Tomás Reyes

Have a stack question we did not cover? Tomás answers these himself.

hello@slipway.studio
Which stack will you use?

Usually Next.js or Nuxt with TypeScript, a headless CMS such as Sanity, and Vercel for hosting. If your team already runs something else, we build on that instead.

Can you take over an existing codebase?

Yes. We start with a one-week audit, tell you what to keep and what to replace, and price the work from there.

Who hosts the site, and who pays for it?

You do, on accounts in your company name. Most marketing sites cost under $50 a month to run. We set up billing alerts before launch.

Will my team be able to edit content?

Yes. We design the page blocks with your marketing team and train them before launch, so new pages ship without a developer.

How do you protect our search rankings?

We map every old URL to a new one, carry over titles and meta, and watch Search Console daily for the first month after launch.

What happens after the 30 days of support?

You can keep the code and run it yourselves, or move to a Retainer at $8k a month for new features and upkeep.

Tell us about your site or app.Get a scoped plan and a fixed quote.

Send a link and a launch date. Tomás replies within one working day.