Imran Khan
A closer look at the build.
The engineer's own site - the catalog's philosophy applied to one career.
Explore the product- Product
- Imran Khan
- Focus
- The maker
- Explore this story
- The problem, the product & the details ↓
The maker
This catalog was commissioned by Imran Khan, a full-stack engineer in Mumbai, and his own site belongs in it: it is built to the same standard as the client work. The hero states the focus plainly - Full-Stack Engineer, AI Backend - building secure SaaS products, booking apps, billing tools and realtime features.
Counts first, then engineering notes
The proof is structured as counts before claims: 150+ features shipped, 24 projects, 4 hackathons, 5+ companies, 60+ production issues resolved. The experience section reads like engineering notes rather than a resume: at Boston Institute of Analytics India, backend engineering on MedConnect across article publishing, job discovery, resume workflows, feeds and media delivery - including a notification module and a networking module built end to end, with database transactions, row locking and Celery email tasks queued after commit.
Previously, at SvayambhuTech, he worked on DriveAccessible - the fleet and rental operations platform featured earlier in this catalog, so the maker's history and the studio's output cross-reference each other.
Why it matters here
A catalog of 33 builds means more when you can see the person behind the keyboard. This site closes the loop: same craft, same honesty about numbers, applied to one career.
Planning a similar build
Bring us the workflow you want to improve. Tell us who does the work today, which tools need to connect, and what your team needs to see in a first working version.
- Define the first useful workflow. Use Imran Khan as a starting point. Choose the task your users need to complete and agree what a successful result looks like.
- Shape the screens around that task. Review a working prototype with your team. Decide what information each person needs, what they can change, and what happens when a step fails.
- Connect, test, then launch. Agree the data and integrations in scope. Test with representative examples on phones and desktops, then document how your team will run and maintain the product.
This is a proposed approach for a custom project, rather than a claim that every feature is included in the public demo.
About this case study
Our look: the full portfolio site.
Have a similar challenge?
Let’s build your solution.
Bring us the workflow you want to improve. Tell us who does the work today, which tools need to connect, and what your team needs to see in a first working version.