How I Work - Amar Harolikar

Best used with an AI agent

40+ live apps, open data APIs, MCP servers, and 200+ guides - more than anyone wants to click through. Point your AI here and it reads the whole map and does the work: finds the tool, pulls the data, runs the analysis, and hands you the links.

Here for the open-source code? Your agent finds the right repo for you - and can even clone and deploy it.

Prefer to explore on your own? Go right ahead.

Paste this to Claude Code, Codex, or any AI agent:

Go to tigzig.com and read tigzig.com/llms.txt. It is a practitioner toolkit - 40+ analytics apps, open no-auth data APIs, MCP servers, open-source repos (github.com/amararun), and 200+ build guides. Help me [your task]. Surface the exact links; where there is an API or MCP, call it directly; and if I want to self-host, find the repo and help me deploy it.

The work

Two kinds, same projects. Analytics, data science, automation, full-stack tools. Built for 10, 20, 50 people .. not apps for millions.

Sessions

Hands-on, over screen share. I work through your actual problem with you and get you up to speed on the tool .. Claude Code in VS Code, the Claude app, Claude in Excel and PowerPoint. What I cover is your call: frontend, backend, databases, models, pulling data from different sources, a full analysis end to end.

For senior folks who want the architecture and the flow more than the keystrokes, I cover that too. But the sessions still center on you using the tool .. that is what makes the time pay off. You want to use it for your own work, and understand how your team works with it.

Execution

I build it. Database AI, report generators, machine learning models, automations, dashboards, full-stack apps with auth and access control. The heavy lifting and the tedious pieces that take time to get right. Same projects as the sessions .. I just do the work.

How execution works

Billed on brain time, not the clock

I charge for the time I am actually on your project .. planning, reviewing, validating, verifying output. Claude Code does the heavy lifting on its own. I might be at my desk 10 hours running three projects, you get charged for the hours on yours, not the wall clock.

Every sprint is pre-approved

Before a sprint I tell you roughly what I am planning. You approve an upper limit, say 3 to 5 hours or 5 to 10. I stop at that limit and report back. No runaway bills, no surprises. The plan is the intent .. what I aim to do within the cap. You see both up front.

The repo is yours. You can take over any time

Repo and documentation sit with you, or you have full control. Stop the project, pick it up later, hand it back .. no issue either way. Most of my clients work with Claude Code too, so the handoff stays clean. Same docs, same tool.

It goes live early, and I stay on it

These are not month-long builds handed over at the end. Your real users, usually a CXO's team, are on the app from 30 to 40% in, the moment basic flows work. So by the time we reach 90%, most of their issues are already fixed and it is in real use .. days to weeks, not months. The small final tweaks, mostly UI, I encourage you to take on because it is faster and cheaper for you. But I keep supporting it through full rollout and beyond, stepping in whenever you want.

Rates

SessionsAI-coder training, setup help, build guidance

$180 / hr

ExecutionBuild work, charged on brain time

$60 / hr

Rates vary by region and engagement. The above are indicative.

All sessions and execution are prepaid .. PayPal, Razorpay, UPI, or bank transfer, whichever works for you.

Availability

Mode

100% remote.

Calls

1 to 6 PM IST. Wednesday to Saturday, typically.

Always open, but I respond during the call windows above.

Queue

Schedule runs full most weeks. I take on what I can fit.

Timelines

I work to my own schedule, and in practice it's fast. But no urgent or fixed-deadline work, even for regular clients.

Get in touch

Reach me on LinkedIn or at [email protected]. Tell me what you are trying to build and a rough sense of scope.

This is a different way of working than the old project-quote model. It only works if you are comfortable with hourly, sprint-capped, repo-in-your-hands, and live before it's finished. Suits some setups, not others - happy to talk through whether it fits yours.