Web apps
Customer portals, marketplaces, internal tools. Built in React and Next.js with the accessibility and performance work done during the build, not filed for later.
Gevix is a studio of eleven designers and engineers. We take websites, web apps, mobile apps and SaaS platforms from a rough idea to paying customers, and we stick around after launch.
Five kinds of work, one team. Everything starts with design and most of it carries straight on into engineering, so the people who drew the screens are the ones who ship them.
Customer portals, marketplaces, internal tools. Built in React and Next.js with the accessibility and performance work done during the build, not filed for later.
iOS and Android from one codebase with React Native, or native Swift and Kotlin when the app needs the hardware. We handle App Store and Play Store submission.
Multi-tenant products with billing, roles, onboarding and an admin your support team can actually use. We design the pricing page and the upgrade flow too.
Marketing sites, brand sites and launch pages that load fast and read well on a phone. Designed in Figma, built in Framer or Next.js, with a CMS your team can edit without us.
Technical SEO on everything we ship: clean markup, fast Core Web Vitals, structured data and a sensible site map. Plus keyword research and a content plan when you want to grow search traffic on purpose.
Already have engineers? We design, test with users, and hand off a Figma library with a written spec your team can build from.
The same people draw it and build it. Nothing gets lost in between.Most products get worse at handoff: the designer moves on, the engineer guesses. At Gevix the designer sits in the pull request and the engineer sits in the Figma file, from kickoff to launch.
Four projects we're proud of. There are more behind NDAs; ask and we'll walk you through them on a call.
Bookkeeping SaaS for small agencies. We designed and built the product, the Stripe billing system and the accountant portal, then ran the first three months of support alongside the founders.
Customer onboarding cut from forty minutes to six.
Training app for road cyclists with ride plans, a coach chat and Strava import. One React Native codebase for both stores, with a small Node service for the coaching queue.
4.8 stars on both stores and 31,000 installs in the first year.
Dispatch platform for a regional haulage firm: a web console for the office and a driver app with offline proof of delivery. Live positions come from the drivers' phones, not extra hardware.
Replaced three spreadsheets and a WhatsApp group for 140 drivers.
An architecture studio in Bergen working on homes, schools and small civic buildings.
A new website for an architecture practice: identity refresh, a project archive with 60 case studies, and a journal the partners write themselves. Built in Framer so the studio edits everything without us.
Enquiries up 2.4 times in the first quarter, and every page loads in under a second on 4G.
From the founders and product leads we've shipped with. Ask us for their details; they're happy to take a call.
“They spent the first week in our depot with the dispatchers. The console works the way the job actually works, not the way a diagram says it should. Our drivers, who hate software, use it without being told to.”
“We'd been burned by an agency that handed over Figma files and disappeared. Gevix built the thing, then stayed through the messy first month.”
“Friday demos on a real staging URL meant there was never a surprise. By week ten our beta riders were already using it.”
“We're architects; we care how things look and we're hard to please. The site is the first thing we've had that feels like us, and we publish to it ourselves.”
“They designed our patient portal around what our nurses actually do, not what the old system did. The first version shipped in eleven weeks and we've had two complaints since.”
A deliberately short list. Boring, well-supported tools mean your next engineer can pick the codebase up without us.
Pick the shape that fits where your product is. All three come with a named lead you can message directly, and a weekly written update.
A defined product, a written scope and a price agreed before work starts. The usual way to build a first version.
Best for a new product or a full rebuild
Two to four Gevix designers and engineers working inside your team, month to month, on a plan you set each week.
Best for growing a product after launch
Two weeks from a problem statement to a clickable prototype tested with five users, plus an honest build estimate.
Best for deciding what to build first
If yours isn't here, the first call is free and we'll answer it there.
Yes. About half our projects are first versions for funded startups. We'll tell you honestly if a two-week design sprint is a better first step than a full build.
Yes. We start with a two-week audit of the codebase and the design, then propose what to keep, what to fix and what to rebuild, with a cost for each.
You do, from day one. Code lives in your GitHub organisation and the Figma files sit in your workspace. If we part ways, nothing needs to be transferred.
Fixed-scope projects get a fixed price after discovery. Monthly teams are a flat rate per person per month. We don't bill by the hour.
The technical side is included in every website and web app: semantic markup, fast load times, structured data, meta tags and a site map. Keyword research, content planning and ongoing optimisation are a separate monthly engagement.
Thirty days of fixes are included. After that, most clients keep a smaller monthly team; the rest take a full handover with documentation and a recorded walkthrough.
Notes from the studio on process, design and engineering. Written by the people doing the work, not a content team.
Waiting for every screen to be finished before writing code is how projects slip. Here's how the overlap actually works.
Most products get worse the moment a designer hands over a file. We stopped handing over.
One codebase for both stores is the default. These are the four cases where we don't.
A few lines about the product, who it's for and when you'd like it live is plenty. A partner reads every message and replies within a business day, usually the same afternoon.