Skip to content
Leapwind

Services

What we build, and what we maintain

Four ways we build software, and three ways we keep it running once it is yours. Every engagement is scoped in writing before it starts.

Build

Software designed and delivered from scratch, or added to what you already run.

Custom Web Applications

Purpose-built software for workflows that spreadsheets and SaaS tools can no longer handle: dashboards, portals, internal tools, and full products.

Typically 6–16 weeks from kickoff to launch, then ongoing support.

What you get
  • Product scoping and technical architecture
  • Full-stack development with typed, tested code
  • Role-based access, audit trails, and admin tooling
  • Deployment and managed hosting on Cloudflare, Railway, or AWS
  • Documentation and handover

Website Development

Marketing sites, content platforms, and storefronts that load fast and get found, built on a CMS your team can actually use, with technical SEO handled during the build rather than bolted on later.

Typically 3–8 weeks from kickoff to launch.

What you get
  • Design and build, from marketing site to full content platform
  • CMS setup so non-technical staff can publish without a developer
  • Storefronts and payment gateway integrations
  • Technical SEO built in: structured data, sitemaps, rendering strategy

Cross-Platform Mobile Apps

One codebase, both app stores. Native-feeling iOS and Android apps built with React Native or Flutter, from customer-facing products to field-team tools.

Typically 8–16 weeks from concept to app-store launch.

What you get
  • iOS and Android from a single codebase
  • App Store and Play Store submission handled
  • Offline-first data sync and push notifications
  • Over-the-air updates after launch

API Design & Integrations

Clean, documented APIs and reliable integrations that make your systems talk to each other: CRMs, payment providers, logistics, and legacy software.

Scoped per integration; most ship within 2–6 weeks.

What you get
  • REST/GraphQL API design and implementation
  • Third-party integrations with retry and failure handling
  • Webhook infrastructure and event pipelines
  • API documentation your team can actually use

Run

Keeping software healthy after launch, and leading the team around it. That is where most of a system's life is actually spent, and where most partners have already gone quiet.

Performance Engineering

Technical audits and hands-on fixes that make software you already run measurably faster: Core Web Vitals, rendering strategy, and the slow paths nobody has had time to chase.

Audit in week one; remediation typically 2–4 weeks.

What you get
  • Performance audit with prioritised fixes
  • Core Web Vitals remediation (LCP, CLS, INP)
  • Rendering and caching strategy
  • Before/after measurement report

Fractional Engineering Leadership

Senior engineering leadership without a full-time hire. We own technical direction, hiring, and delivery process for teams that need a head of engineering before they can justify one.

Ongoing, typically 1–3 days a week over 6–12 months.

What you get
  • Technical direction, architecture, and roadmap ownership
  • Hiring: scorecards, interview loops, and onboarding
  • Delivery process, 1:1 cadence, and career frameworks
  • A team that can run without us when the engagement ends

Maintenance & Support

Long-term care for software you depend on: monitoring, security updates, incremental features, and a team that already knows your codebase.

Monthly retainers with a guaranteed response window.

What you get
  • Managed hosting, deployment pipelines, and uptime monitoring
  • Error alerting with a named owner for each alert
  • Dependency and security updates
  • Monthly improvement capacity
  • Priority response for incidents

How we build it

The tools behind the work

A deliberately small set, kept small on purpose. We would rather be genuinely deep in a few technologies than pass ourselves off as competent in everything.

Languages and runtimes

Two languages, used everywhere. Typed by default on the JavaScript side, so the compiler catches what a reviewer would otherwise have to.

  • TypeScript
  • JavaScript
  • Node.js
  • Python

Frameworks and platforms

What we reach for first, chosen per project rather than by habit. Next.js, TanStack Start, and Astro are React underneath; Frappe is Python, and ERPNext is the business suite built on it.

  • AdonisJS
  • Next.js
  • Astro
  • TanStack Start
  • Frappe
  • ERPNext

Infrastructure and data

We deploy and run what we build, rather than handing over a repository and wishing you luck. Managed platforms by default, because paying a provider to run the boring parts is cheaper than paying us to.

  • Cloudflare
  • Railway
  • AWS
  • PostgreSQL
  • MongoDB
  • Redis

Not sure which service fits?

Describe the problem. We'll tell you honestly what we'd build, and what we wouldn't.

Start the conversation