[ android apps · websites · dashboards · ai workflows · automation ]
Need something built? Let's talk it through.
We build and design apps, websites, dashboards, automations, integrations for founders and small businesses, start to finish. Just tell us what you need.
prospective client, 11:42pm
“need something for my delivery guys, they scan stuff and idk maybe a dashboard too, nothing fancy”
The structured spec
{
type: "Android app + web dashboard", users: "field staff, ops team", core: ["camera capture", "OCR", "sync"], status: "buildable",}[ what we build ]
Concrete software, not consulting slides.
You don't need a technical spec to start. Bring the requirement — we'll help structure it, build it and deploy it.
Android/iOS Apps
For field teams, inspections and internal operations.
Websites & Web Apps
Business sites, customer portals, admin dashboards and functional web tools.
Internal Tools
Approvals, tracking, inventory, review queues, ops dashboards.
AI & Automation
AI-assisted workflows and integrations — used where they genuinely help.
OCR & Document Processing
Extraction, classification and validation from PDFs, forms and images.
Computer Vision
Number-plate recognition, image-based verification, object detection.
Integrations
Connecting the tools you already use — APIs, CRMs, WhatsApp, email.
MVP Development
A working first version to test or operationalise an idea.
[ why this instead of an agency ]
A small team, accountable end to end.
[ one accountable owner ]
No hand-offs, no re-explaining
One conversation, one point of contact, from the first message to hand-over — not a new account manager every few weeks.
[ not a numbers game ]
A handful of projects, not dozens
We take on a small number of engagements at a time, so yours gets real attention rather than leftover hours.
[ business + technology ]
Starts with what needs to work
The conversation doesn’t begin with a technology choice. It begins with your workflow, your users, and what "done" looks like.
[ built for your workflow ]
Not a generic template
Software is designed around your actual rules, exceptions and operating conditions — not a one-size-fits-all shell.
[ practical use of AI ]
Used where it earns its place
AI and OCR go in when they genuinely improve the solution — not because it's fashionable to mention.
[ experience that shows ]
Built this before
Product, AI and engineering background across companies like Nanonets and MakeMyTrip — not a first attempt at any of this.
[ how it works ]
You send one message. We take it from there.
No procurement process, no account managers — you're talking to the people who actually build it, from the first message to hand-over.
- 01[ you ]
Share what you need
A rough note, a voice message, a WhatsApp text — however it comes out easiest. No spec required.
- 02[ us ]
We come back with a plan
A process map, a timeline, the technical approach, and a straightforward proposal — usually within a few days.
- 03[ you ]
Quick sign-off
A short call or a WhatsApp "yes" to confirm scope. No lengthy contracts to chase.
- 04[ us ]
Build it
Development with internal QA, plus regular check-ins as it comes together.
- 05[ us ]
Test it, then it's yours
You try it out (UAT), then it deploys and hands over — fully yours.
// projects have ranged from a focused couple-week build to a larger multi-month system — happy to figure out the right shape once we understand the ask.
[ collaborators ]
Who might work on this with you.
A small group of people we bring in as projects need more hands. You'll always know exactly who's working on what.
Shivang Shekhar
BITS Pilani '21 · Product & AI at a Y Combinator-backed startup · Founder-led builds
View full profile
[ stack ]
Tools we actually ship with.
Mobile
Backend
Cloud & Data
AI
[ recent work, in more detail ]
A closer look at one build
Vehicle verification & computer-vision workflow for an Indian enterprise
Under developmentThe requirement
- Field staff needed to capture and verify vehicle details on the spot
- Verification had to check against a live external registry
- Results needed to print as a physical receipt in the field
Role on this project
- Discovery, workflow mapping and technical architecture
- Android app design and development, plus backend API
- Computer-vision evaluation and third-party data integration
- Deployment planning across a multi-device rollout
// client name and screens kept private under the engagement's confidentiality terms — happy to walk through more specifics on a call.
[ faq ]
Questions people usually ask first
Straight answers on trust, cost, timeline, ownership and how we work together.
Why should I trust you with a serious project?
We've shipped software and AI products used by real companies — including product and engineering roles at a Y Combinator-backed startup. We've also raised a $250K+ seed round and built a consumer tech product from scratch. On the client side, we've taken projects from a rough requirement through design, build and hand-over — apps, backends and integrations that actually went live. When you work with us, that experience sits with you directly — no account manager, no hand-off, no one else's priorities in between.
How much will my project cost?
Depends on scope, but roughly: a tightly-scoped rapid build runs ₹40,000–₹1,00,000, a proper first version (a few screens, real logic, maybe an integration) runs ₹1.5–5 lakh, and a bigger end-to-end system is ₹5 lakh and up. You won't get a real number until we understand what you're building — anyone who quotes you before that conversation is guessing.
How long will it take?
A rapid build: 1–3 weeks. An MVP: 4–10 weeks. A bigger system: 3 months or more. The plan we send after our first conversation has a real timeline in it, not a placeholder — if we can't commit to a date yet, we'll say that too, instead of promising something we're not sure of.
I don't have a technical spec — can you still help?
Yes — that's the normal starting point, not the exception. Most people who come to us have a rough idea and no idea how to turn it into a spec. Send it however it comes out — voice note, messy WhatsApp text, half-written doc. Turning that into a real plan is part of what you're paying for, not something you're expected to arrive with already done.
Will you sign an NDA?
Yes — signing an NDA is a standard part of how we work with any client, not a special negotiation. We'll sign yours, or use a standard one if you don't have one ready.
Who owns the code once it's built?
You do, fully, once the agreed milestones are paid. We don't retain rights to anything built specifically for you — your app, your data, your business logic, all yours.
What happens after launch — do you disappear?
No, but we're also not offering unlimited free support forever, because that's not sustainable for either of us. Bug fixes on what was actually delivered are covered for a defined window after hand-over (we agree the exact window upfront). New features beyond that are a new, separately scoped piece of work — same process as the first time.
I'm not technical — will I actually understand what's happening?
Yes. We won't explain things in jargon and expect you to nod along. If something technical matters for a decision you need to make, we'll explain what the tradeoff means for your business, not the underlying tech.
Can I bring my own developer or team, and have you work alongside them?
Yes. What we own and what they own gets defined in the plan before any work starts, not figured out midway.
How do I pay — everything upfront?
No. Milestone-based, agreed in the proposal before we start — something at kickoff, the rest tied to defined checkpoints. Not a lump sum at the end, not 100% upfront either.
What if partway through, it's not working out?
You can stop at any milestone boundary. You keep whatever's been delivered and paid for up to that point — no demand to commit to the full scope once you're in.
[ say hi ]
Got something you want built?
Answer a few quick things and send them over on WhatsApp — name, phone, and what you want to build is enough to start.
// usually reply within a few hours.