Skip to content
Services

Seven services. One team that does all of them well.

Most projects use two or three of these together. Tell us the problem and we will tell you which ones you actually need.

01Fast on a mid-range phone

Website Development

Marketing sites and web platforms built for speed, search, and conversion. We test on real devices and slow networks, not just a laptop on office wifi.

Talk about this

What you get

  • Sub-second loads on real hardware
  • Structured for search from day one
  • A CMS your team will actually use
  • Layouts shaped by analytics, not opinions

Built with

  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • Sanity
  • Vercel
02One codebase, two app stores

Mobile App Development

iOS and Android apps that feel native, from a single codebase. Smooth scrolling, sensible offline behaviour, and a release process that does not stall.

Talk about this

What you get

  • 60fps gestures, not a website in a shell
  • Works offline, syncs when it can
  • Push, deep links, biometrics
  • We handle the store submissions

Built with

  • React Native
  • Expo
  • Swift
  • Kotlin
  • Firebase
  • GraphQL
03Interfaces that explain themselves

UI/UX Design

Research, flows, and interface design that make a complicated product feel obvious. You approve every screen before anyone writes code.

Talk about this

What you get

  • Interviews and flows before pixels
  • A design system, not one-off screens
  • Clickable prototypes to test early
  • Contrast and keyboard access built in

Built with

  • Figma
  • Framer
  • Design Tokens
  • Storybook
  • Lottie
04Shaped around how you work

Custom Software

Internal tools, SaaS products, and platforms built around your actual process, instead of bending your team to fit someone else's software.

Talk about this

What you get

  • Architecture that survives growth
  • Dashboards your ops team will open daily
  • Roles, permissions, audit trails
  • Documented code you own outright

Built with

  • Next.js
  • Node.js
  • PostgreSQL
  • Prisma
  • Redis
  • AWS
05The part that survives production

AI Integration

Copilots, semantic search, and automation that hold up with real users. We deal with the unglamorous half: evals, guardrails, and the monthly bill.

Talk about this

What you get

  • Assistants grounded in your own data
  • Search that understands intent
  • Automation that removes real hours
  • Cost and quality monitoring

Built with

  • Claude
  • OpenAI
  • LangChain
  • Pinecone
  • Vercel AI SDK
06The layer everything leans on

API Development

REST and GraphQL services built to stay up under load, and documented well enough that another team can build on them without calling you.

Talk about this

What you get

  • Versioned endpoints with real docs
  • Integrations and webhooks
  • Caching, rate limits, retries
  • Alerts that fire before users notice

Built with

  • Node.js
  • GraphQL
  • tRPC
  • PostgreSQL
  • Docker
  • Kubernetes
07Still here after launch

Maintenance & Support

Monitoring, updates, and steady improvement, so what we built keeps getting better instead of quietly rotting for two years.

Talk about this

What you get

  • Uptime monitoring and alerting
  • Security and dependency updates
  • Performance kept in check
  • A team you can just message

Built with

  • Sentry
  • Datadog
  • GitHub Actions
  • Vercel
  • Cloudflare
How it goes

Ten weeks, five stages, no black boxes.

You see working software every two weeks and can change direction while it is still cheap to do so.

  1. Discover

    Week 1

    A week of questions. We map goals, users, and constraints, then send back a scope, a timeline, and a fixed price.

  2. Design

    Weeks 2 to 3

    Flows first, then wireframes, then finished UI in Figma. Nothing gets built until you have seen it and signed off.

  3. Build

    Weeks 4 to 9

    Two-week cycles, each ending in a working demo you can click. You steer while it is still cheap to change course.

  4. Test

    Week 10

    Real devices, edge cases, accessibility, and load. We would rather find the ugly problems than have your users find them.

  5. Launch

    Ongoing

    We deploy, watch the graphs, and fix whatever surfaces in the first weeks. Then we sit down and plan what is next.

Stack

Boring technology, chosen on purpose.

We pick tools with long support horizons and large hiring pools, so you are never stuck with something only we can maintain.

Frontend
Next.jsReactTypeScriptTailwind CSSFramer Motion
Backend
Node.jsGraphQLtRPCPythonGoPostgreSQL
Mobile
React NativeExpoSwiftKotlin
AI and data
ClaudeOpenAILangChainPineconeRedis
Cloud and ops
VercelAWSDockerCloudflareGitHub Actions
Design
FigmaFramerStorybookSpline
Questions

The things people ask before signing.

Something not covered here? Email us and you will get a straight answer, not a sales sequence.

Most websites land between 8K and 20K. Apps and custom software usually start around 25K and go up with scope. After one call we send a fixed price, and it does not move unless you change what you asked for.

Not sure which of these you need?

Most people are not, and that is fine. Describe the problem in a couple of sentences and we will tell you what we would do, even if the answer is that you do not need us yet.