No form maze. No discovery-call funnel. No “a member of our team will be in touch.” You write to mohit@empyrealinfotech.com. Mohit reads it. Mohit writes back. The first three exchanges decide whether we’re right for each other.
The strongest first emails are short, specific, and honest about what the founder doesn’t know yet. Here’s the anatomy, so you don’t spend an afternoon on a doc you didn’t need.
“Hi, we’re building a product and looking for a development partner. Can we set up a call to discuss our requirements?”
Reads like a procurement form. No category. No timeline. No problem. The reply will be 30 questions, and you’ll spend another week answering them.
“Hi Mohit. Series A B2B SaaS, 9-month-old codebase in Next.js and Postgres. We’re onboarding 60 enterprise customers in Q4 and the auth + tenant model is going to fight us. Two of our senior engineers are leaving. We need an architectural audit by 12 Sep, then 4 engineers slotting in for 8 weeks. Budget around £90K. Can we talk Tuesday?”
Six specifics. Stage, stack, real problem, real date, what’s leaving, what’s needed, a budget. Mohit can give you a useful reply on the first pass.
Put these in, in any order, and the first reply will be useful instead of a list of questions back at you.
“Fintech onboarding,” “B2B SaaS auth,” “AI workflow tool.” One line is enough.
Pre-seed, Series A, scale-up, established. We staff differently for each.
Not the feature. The thing that’s about to break, the deadline that’s about to hit, the team that’s about to leave.
Audit, build, pod, advisory. Don’t worry if you can’t name it — we’ll pick one in the call.
Even a rough one. Saves three emails on both sides.
No mystery. No “we’ll get back to you when we can.” Here’s the actual rhythm so you know exactly where things stand.
It’s in Mohit’s personal inbox. No router, no triage layer, no “account manager”. If it’s working hours in London, he’s probably already read it.
One of three answers. A “yes, let’s talk, here are Tuesday slots.” A “not the right fit, here’s why, and here’s a studio I’d call instead.” Or one question that decides it.
If the answer was yes, you book a 30-minute first call in the calendar Mohit shares. No sales sequence, no auto-follow-ups. If the answer was no, you keep the honest paragraph and we both move on.
Most often: a 30-minute call where Mohit asks the 7 questions in the next section and tells you which engagement shape would fit. Sometimes: a one-page written diagnosis instead, when a call is the wrong tool for the question.
Scope, weeks, named seniors, weekly cadence, walk-away clauses, pricing in GBP. No 40-page master services agreement. The whole document is short enough to read on a train.
The first call is 30 minutes. Mohit will work through these seven questions with you, in roughly this order. You don’t need answers for all of them. You will get more out of the call if you’ve thought about three or four.
One focused call
Asked in order
“You don’t need answers for all of them. You’ll get more out of the call if you’ve thought about three or four.”
Most founders arrive one of three ways. None of them is better. The shape of the engagement is decided after the first call, not before.
Two weeks. Senior engineer pair. We read what you’ve built, draw the system as it should be, and hand back a short report with the trade-offs named, the rebuilds prioritised, and the timeline costed.
2 to 6 senior engineers slotting into your codebase under one of our principal engineers. We pick the model in the audit week: pod that owns surface area, paired-engineer with your team, or architecture-only with you shipping.
Weekly standup with your CTO. Quarterly architecture review with the founder. The call before the next round of feature creep. We treat this as the highest-leverage relationship we can be in. It’s where the year-two bugs get caught in week one.
About one in three projects we hear from, we turn down. We do it in the first reply, with a paragraph explaining why. Here are the three most common reasons, so you can decide before you write.
The right move is to ship the cheapest version yourself first, find real signal, then talk to a studio. We’d rather lose the contract than spend your runway on engineering you don’t need yet. We’ll point you to a builder who works at that stage and stays cheap.
Hardware-first robotics, AAA game engines, regulated medical devices, large-scale platform research. Not our work. We’ll name a studio who does it better than we ever could, and the introduction is free.
“Just start shipping, we’ll figure it out as we go.” The diagram and the trade-offs come first. Every time. If that’s a no for you, we’re the wrong studio, and we’ll say so before the contract.
The studio gets approached by founders who’ve been burned before. So we wrote down what we do with whatever lands in the inbox, without making you ask.
Anything you put in the first email is treated as confidential by default. We’ll sign your NDA before the first call if you want one, and we keep a one-page mutual NDA on hand if you don’t.
We don’t take credentials in email. Repo access is granted to named engineers only. Credentials live in your secrets manager, never ours.
All code, architecture, and documentation produced for you is yours. The MSA assigns IP on commit. There’s no “our framework” clause hiding in the contract.
Every engagement has a 30-day walk-away clause from either side, with a written handover at the end. If we’re wrong for each other, the relationship ends cleanly.
UK GDPR. Data Processing Agreement available on request. We don’t train models on your data, ever. If we use any AI tool on your code, you approve the tool list in writing first.
The questions that come up most often when someone’s reading this page, thinking about whether to write.
Mohit Ramani, the founder. Not an assistant, not a router, not an automation. The first reply you receive comes from him personally, written after he’s read what you sent and thought about whether the studio is the right shape for the project you described.
Inside 24 hours on weekdays. Inside 72 hours over weekends and the brief annual studio break in late December. If the reply will take longer than that, you’ll get a one-line acknowledgement with a date by which a real reply is coming.
Send the email. The studio’s smallest engagements are 2-week audits at around £8,000. The largest are multi-year builds. About a quarter of the projects we take are under £30,000 total. If we’re wrong for the size of the work, we’ll say so and point you to a builder who fits better.
Write the email anyway. The 30-minute first call is, more than anything else, a diagnosis call. Mohit will work through the 7 questions in the section above and tell you which shape of engagement would actually fit. Sometimes the answer is “not us, here’s who.” Sometimes it’s “not yet, here’s what to do first.”
No. The 30-minute diagnosis call is on us. We treat it as part of how we choose work. We don’t do paid “discovery” sequences before we’ve had a real conversation. If a written audit is the right next step, we’ll propose one with a fixed scope and a fixed price.
Yes. Send it as an attachment to your first email. We’ll review it before the call. If you don’t have one, we keep a one-page mutual NDA we’re happy to share before the conversation starts.
UK, EU, North America, India, Australia, Singapore. We work in English and bill in GBP. Most of our clients are in the UK and the US. The two-office model (London + Rajkot) means a senior engineer is on your project across 16 working hours a day.
contact, in context — the dashboards, flows and components your team actually ships, reviews and maintains.