India
Rajkot, Gujarat
Engineering base. Where the build team sits and where most delivery work runs from.
Contact
Talk To Mohit.
Bring a stuck workflow, an AI-built MVP that needs a launch review, or a system that has outgrown the way it was built. You get a direct technical answer from the person who would do the work - not a sales call.
Direct Lines
Two Ways To Reach Me.
No contact form, no ticket queue, no account manager in between. Both of these land with me.
Email
mohit@empyrealinfotech.com
Best for scoping a build, a launch review, a retainer question, or anything with detail attached. Write in as much depth as you like.
Replies in 1-2 working days
Compose email
LinkedIn
Message or follow on LinkedIn
Best for a short question, a quick introduction, or following The Build Notes - the newsletter is published there, not by email.
in/mohitramani
Open LinkedIn
Make It Useful
What To Put In The First Message.
A useful reply needs something to work with. Four lines is enough - a document is not required.
OneWhat is actually happening right now
The system, the workflow, or the product as it stands today. What breaks, what takes too long, or what has not been built yet. Plain description beats a polished brief.
TwoWhat you want to be true instead
The outcome, not the feature list. "Forty manual hours a month should not come back" is more useful than "we need an AI agent".
ThreeWhat already exists
Stack, team size, whether there is a codebase or a blank page, and whether anything was built with AI coding tools. This changes the answer more than anything else in the message.
FourTiming and constraints
Launch dates, budget range, compliance requirements, or a board meeting you are working backwards from. Constraints are not a problem to hide; they are what makes a recommendation realistic.
Where I Work From
Rajkot And London.
Two bases, two time zones, one delivery team. Clients sit across India, the UK, Europe and the US.
United Kingdom
London
Client-facing base. Useful for UK and European founders who want overlapping hours and someone in the same time zone.
What Happens Next
No Funnel. Just A Reply.
Step 01You get a real answer, not a calendar link
The first reply comes from me and addresses what you actually wrote. If the honest answer is that this is not the right fit, you get that too, usually with a pointer towards what is.
Step 02A call only if a call adds something
Plenty of questions are settled in two emails. Where a conversation genuinely helps, we book 30 to 45 minutes and go straight into the technical detail.
Step 03Scope in writing before anything starts
If there is work to do, it gets written down first - what is included, what is not, what it costs and who owns what. Nothing begins on a handshake and a hope.
Elsewhere
The Rest Of The Internet.
Same person, different rooms. Email is still the fastest way to get a considered answer.
Instagram
@mohitramaniofficial
Behind the build - team, travel and the day-to-day of running an engineering company.
Twitter / X
@mohit_empyreal
Short takes on AI tooling, engineering cost and what is actually shipping.
Facebook
mohitramaniofficial
Longer updates and announcements for people who keep up there.
The Build Notes
Read the newsletter
Weekly notes on software cost, AI automation and production reality. Published on LinkedIn, indexed here.