Skip to content
Taking on new projects. Send us a brief
galenry.
Diagnose. Design. Deliver.

We find the root cause before we build anything

Custom software and AI for teams who need a problem solved for good. We diagnose first, design against what we find, and deliver it to production.

Send us a briefSee our work
Client systems live
2
Products we run
2
How we work
Problem
Checkout times out and orders fail on screen.
Finding
Root cause found: a blocking call in the queue.
Work

Systems running in real businesses, and we can walk you through every decision.

View all work
Appooppanthaadi homepage: a women-led group on a hillside under the headline “Your turn to go after everyone else”, with ratings and trip counts.
The Appooppanthaadi homepage on a phone.
Appooppanthaadi01 / 02

Self-serve booking, and an AI that isn’t allowed to guess

A women-led travel company was handling every trip by hand. Now customers book and pay online, and an AI assistant answers from live data, checking every figure first.

What we solved

  • Customers book and pay online themselves
  • Seats released if a payment never completes
  • Every custom enquiry tracked to a 48-hour reply
  • Cancellations with clear options: transfer, credit or refund
  • AI answers checked against live data before they are shown
Read the case study
What we do

Six practices, one team accountable from diagnosis to production.

AI Product Development

AI features customers can rely on: answers from your own data, tested before release, inside limits you set.

Includes:
  • Assistants and agents
  • Search over your own data
  • Testing before release
  • Model fallback

Digital Experience & Platforms

Websites, apps and portals that stay fast, accessible and easy to change as your business grows.

Includes:
  • Web and mobile products
  • Design systems
  • Accessibility and performance checks
  • Content your team can edit

Enterprise Architecture

A clear plan for systems that have outgrown themselves, and a way to modernise them without stopping the business.

Includes:
  • System design
  • Phased migration
  • Data and integration design
  • Written decisions

AI Automation & Transformation

Manual work handed to software, with a person on the uncertain cases and a record of every decision.

Includes:
  • Process review
  • Human review steps
  • Audit trails
  • Measured savings

SaaS Product Engineering

The foundations a subscription product runs on: customer separation, billing, onboarding and safe releases.

Includes:
  • Multi-tenant platforms
  • Usage and billing
  • Customer onboarding
  • Controlled rollouts

Cloud & DevOps Excellence

Automated releases, monitored systems and infrastructure you can rebuild, so shipping stops being an event.

Includes:
  • CI/CD pipelines
  • Infrastructure as code
  • Code and security scanning
  • Monitoring

Not sure where to begin?

Start with a discovery phase. We map the problem, the constraints and your existing systems, and you keep the technical roadmap whether or not you continue with us.

Explore all practices
Process

Every step ends with something in your hands.

At each stage you get something you can review, so you always know where the work stands.

  1. 01

    Diagnose

    You get: A written diagnosis

    We learn your goals, your constraints and what has already been tried, then find what is really causing the problem.

  2. 02

    Plan

    You get: A technical roadmap

    We decide what to build first and how the pieces fit together, so you see value early and know the route ahead.

  3. 03

    Design

    You get: Screens and a design system

    We design with your real content and the awkward cases, so there are fewer surprises later.

  4. 04

    Build

    You get: Working software

    You review working software in regular stages, with automated tests in place from the very start.

  5. 05

    Launch

    You get: A live system

    We release to production with monitoring, a way to roll back, and a runbook your team can follow.

  6. 06

    Improve

    You get: Measured results

    We measure results against the goal set at the start, then improve whatever the data points to.

See it on a real project

The Dayone case study follows the whole journey: the problem, what we built, and how an order now becomes a production plan and a stock movement.

Read the Dayone case study
How we build

Built for the five years after launch. Every layer has one rule it has to keep.

Review your architecture
01What people use

Web & mobile

Fast on every device, checked on every release

We set a speed limit for every page and check it automatically each time something changes. A release that makes the product slower or harder to use is caught before your customers see it.

  • Next.js
  • React
  • React Native
  • TypeScript
  • JavaScript
  • Tailwind
02What people use

APIs

New versions never break what already works

Your web app, mobile app and partners all depend on these connections. We version them, so what you already have keeps working while new features roll out alongside it.

  • GraphQL
  • REST
  • BFF pattern
03What does the work

Services

Each part can change and ship on its own

We divide the system along clear business boundaries, such as orders, stock and billing. Each can be improved and released without waiting for the others, and a change in one is far less likely to disturb the rest.

  • Node.js
  • NestJS
  • Python
  • Microservices
  • Serverless
04What does the work

AI

Answers come from your own data

The assistant searches your own approved content before it answers, and shows where each answer came from. When it isn’t confident, it hands over to a person instead of guessing.

  • OpenAI
  • Claude
  • RAG
  • pgvector
  • Pinecone
  • AI agents
05What it stands on

Data

Proven databases first, caching only where it helps

We start with reliable, well-understood databases and a carefully designed data model. Caching is added only where a slow request actually needs it, so there is less that can go wrong.

  • PostgreSQL
  • SQL Server
  • MongoDB
  • Redis
  • Object storage
06What it stands on

Content

Your team edits once, and it appears everywhere

Content is structured once in a CMS your team controls, then delivered to your website, app and other channels. Everyday updates don’t need a developer or a new release.

  • Payload CMS
  • Strapi
  • Sanity
07What it stands on

Platform

Releases are routine

Building, testing and deploying are automated, and infrastructure is defined in code. That keeps releases small and frequent, with monitoring in place and a quick way to roll back.

  • AWS
  • Azure
  • GCP
  • Vercel
  • Terraform
  • Docker
  • Kubernetes
  • CI / CD
What we build with

Engineering first, with AI applied where it earns its place.

  • LanguagesTypeScript, JavaScript, Python, SQL
  • Web & mobileNext.js, React, React Native
  • ServicesNode.js, NestJS, Python
  • DataPostgreSQL, SQL Server, MongoDB, Redis
  • AI modelsClaude, OpenAI
  • AI toolingRAG, pgvector, Pinecone, AI agents
  • CloudAWS, Azure, GCP
  • InfrastructureDocker, Kubernetes, Terraform
What we run

We carry the pager for our own advice. Two products we build and operate ourselves.

View all products
Customer Supportlive

Answers from your own docs

Chat that answers from your own content, and hands off to a person before it guesses.

  • Answers from your content
  • Hand-off to a person
  • Confidence limits
Travel Assistantlive

Finds the trip, then hands it over

Finds tours, packages and itineraries in conversation, and hands anything that needs a commitment to your team.

  • Finding trips in conversation
  • Day-by-day itineraries in chat
  • Tracked hand-off to your team
FAQ

Common questions, plainly answered

What people usually ask before a first call. If yours isn’t here, ask us directly.

What does an engagement usually look like?

Most start with a discovery phase: we map the problem, the constraints, and the architecture, and you get a technical roadmap you own whether or not you continue with us.

How long will a project take?

It depends on what discovery finds, so we don’t quote a standard timeline. You get a plan and a sequence before building starts, then review working software in regular stages.

How quickly will you reply?

Within one business day, and from an engineer rather than an autoresponder. The first call is 30 minutes, with no deck.

Do you work with early-stage companies?

Yes. We are early ourselves. What matters is whether the problem is real and whether you can act on the answer.

Can you take over an existing codebase?

Often. We start with an audit and tell you plainly whether it is worth continuing or rebuilding, including when the honest answer is that it is fine as it is.

Which industries do you know?

Travel, SaaS, retail and fintech-adjacent platforms. We say so plainly when a domain is new to us.

What if you’re not the right fit?

We say so on the first call and, where we can, point you to someone better suited.

Get started

Tell us what you’re trying to build. We’ll tell you where we’d start.

Bring an idea, a stalled project, or a system that has outgrown itself.

Send us a brief

The problem, what you have tried, and what success looks like. A few lines is enough to start.

Send us a brief

Prefer email? contact@galenry.com

What happens next

  1. 01Reply within one business dayFrom one of our engineers.
  2. 02First call: 30 minutes, no deckA working call about the problem. We ask questions rather than present slides.
  3. 03An honest answerWhere we would start, or, if we are not the right team, who might be.