galenry.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. A few lines is enough to start.
What happens next
- 01Reply within one business dayFrom one of our engineers.
- 02First call: 30 minutes, no deckA working call about the problem. We ask questions rather than present slides.
- 03An honest answerWhere we would start, or, if we are not the right team, who might be.
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.
Do we actually need AI?
Not always. We are engineering first and apply AI where it earns its place. If a simpler system solves the problem, that is what we will recommend.
How do you stop AI making things up?
Answers are built from your own approved content and show where they came from. Anything it isn’t confident about goes to a person, and every prompt or model change is scored against a fixed test set before release.
Can you work with our existing systems?
Yes. We map what exists first, then move one area at a time while the old system keeps running, so the business doesn’t have to stop for the change.
Which technologies do you use?
Mainly TypeScript, React, Next.js, Node.js, Python and PostgreSQL, on AWS, Azure or GCP. We fit the choice to your system and your team, and we don’t leave you with tooling only we can operate.
Who owns the code?
You do. Source, infrastructure definitions and documentation are yours, in your repositories.
Will you sign an NDA?
Yes. We sign your NDA and DPA.
How do you handle our data and access?
Least-privilege access and short-lived credentials, and no production data copied to local machines.
What happens after launch?
You get monitoring, documentation and a runbook your team can follow. If you would rather we stayed involved, we can continue on a retainer.
How do you charge?
Retainer or fixed-scope project, agreed before we start. No hourly billing and no change requests for things that were always going to be needed.
Are we locked in?
No. There is no lock-in period, and the system is built so your team or another supplier can take it over.
Where are you, and what currency do you quote in?
We are remote-first and registered in India, working across IST with overlap into European and US mornings. We quote in USD by default, and in INR or EUR where that suits you better.