Services
Fixed scope, fixed quote, one developer who owns the whole path.
I take on a small number of projects alongside my role at Lincole Group — the kind where one person who understands the frontend, the API, the database and the deployment is faster than a team handing work across boundaries. Each package below is a starting shape; the quote is written for your project after a short call.
Internal system or ERP module
Businesses running operations on spreadsheets, WhatsApp and memory.
Orders, inventory, invoicing, students, staff — one system with the right people seeing the right things, and reports that used to take a day available in a click.
- Data model and permissions designed around how the business actually works
- Web app for the office; mobile apps where a phone is the real device
- Dashboards, exports and PDF documents (invoices, reports, receipts)
- Migration from the spreadsheets you have today
- Deployment, backups, and a handover the next developer can read
3–8 weeks depending on modules · fixed quote after a short call
MVP or SaaS in 4–6 weeks
Founders who need a real product in front of users, not a prototype.
A production build from day one — auth, database, billing-ready structure, deployment — so the thing you validate is the thing you scale.
- Scope cut to what the first users need; the rest written down for phase two
- Next.js + Postgres (Supabase or managed) with auth and roles
- Deployed on Vercel or Google Cloud with monitoring and error tracking
- Weekly demos; you see it working every Friday
- Your repos, your accounts — you own everything from the first commit
4–6 weeks · fixed quote after a short call
AI feature or tool
Teams that want an LLM feature that survives contact with real users and real bills.
Classification, extraction, summaries, assistants — built with quotas, caching, fallbacks and validated outputs, so it's a product and not a demo.
- Model choice for the job (Gemini, OpenRouter models, Claude) and prompt design
- Structured, validated outputs your UI can trust
- Rate limits, per-user quotas, caching and model fallbacks
- Evaluation set so you know when a change made it worse
- Regional-language handling where it matters (Malayalam, Manglish)
2–4 weeks · fixed quote after a short call
Security review of your web app
Anyone about to launch, raise, or onboard a client who will ask "is it secure?"
A pentester's eyes on your own product: what is exposed, what can be abused, and a fix list in priority order — written for developers, not auditors.
- External recon: what your app leaks about itself (subdomains, headers, endpoints, secrets in JS)
- Authentication and authorisation review — the bugs that actually get exploited
- Dependency, configuration and header hardening
- A written report with reproductions and fixes, then a re-check after you patch
- Optional: I fix the findings myself
About a week · fixed quote after a short call
See:ShadowHound
How it runs
- 01
Call
Twenty minutes. You describe the problem; I ask the awkward questions early.
- 02
Scope & quote
A one-page scope with what's in, what's out and a fixed price. No surprises later.
- 03
Build in the open
Weekly demos on a live URL. You use the software while it's being built.
- 04
Handover
Your accounts, your repos, a README that explains the thing, and a month of fixes.
Questions I get asked
Do you work with clients outside India?
Yes — most work is remote. I'm on IST (UTC+5:30), which overlaps the European morning and the whole Gulf working day.
How do you price?
Packages are a fixed price for a fixed scope, quoted after a short call. Ongoing work — a system that keeps growing — runs on a monthly retainer. I don't bill by the hour, because it rewards the wrong thing.
Who owns the code?
You do. Work happens in your GitHub organisation and deploys to your Vercel or Google Cloud account from the first week, so there is nothing to hand over at the end.
Can you work with an existing codebase or team?
Yes. My day job is full-stack development inside a company, so joining an existing stack, review process and deployment pipeline is normal. I'll tell you honestly if a rewrite is cheaper than a rescue.
What do you build with?
TypeScript end to end — Next.js and React on the front, Node or FastAPI APIs, PostgreSQL (often via Supabase) underneath, Docker where it helps, deployed on Vercel, Google Cloud or Cloudflare. Python where it earns its place, especially for security tooling and data work.
Are you available right now?
I keep one or two client projects running alongside my role at Lincole Group. Book a call and I'll tell you the earliest start date the same day.
Tell me what you're building.
Twenty minutes, no deck. If it isn't a fit I'll say so and point you somewhere better.