Clarify the constraint
Identify the input, decision points, edge cases, authoritative records, and success metric before talking about a build.
I’m Anish Jhaveri, an independent software engineer in Austin. I work directly with founders and product teams to turn unclear workflows, product requirements and technical constraints into maintainable software.
HOW I WORK
My background spans accounting, business operations and software development. That combination is useful when the work touches the parts of a business that software has to respect: source-of-truth data, approvals, exceptions, handoffs, reporting, internal controls and the people who operate the workflow every day.
I turn a business requirement into a scoped build: the workflow, system boundaries, data involved, risks, milestones and the smallest useful first release.
I build and extend web applications across UI, APIs, integrations, databases and operational tooling, whether the work starts with an idea, an existing product or a system that has outgrown its first implementation.
I use retrieval, document search, structured workflows and automation where they create a measurable improvement, not as a generic AI layer added after the fact.
I am especially useful where operational data, financial processes, approvals, reporting or reliability constraints shape what the software needs to do. Earlier work auditing and preparing financial statements under GAAP is where that understanding comes from.
Ask questions against Stripe implementation docs and inspect the cited chunks behind each answer. Shows retrieval, bounded search and citation handling running in production.
ScoutLocal · Client case studyNotes from a documented product build involving natural-language search, auth, data modeling, and founder workflows. Shows how a client engagement is scoped, built and handed over.
Technical Decisions · WritingPractical breakdowns on when to use a local or managed model, when deterministic logic is enough, and when custom code is not worth it. Shows the reasoning behind the builds.
Earlier client work, 2010 to 2020. Selected CMS, commerce, integration and client-delivery work from earlier engagements, each dated. View selected client work →
Identify the input, decision points, edge cases, authoritative records, and success metric before talking about a build.
Use deterministic rules, integrations, search, or AI only where they make the workflow easier to run and review.
Deliver source code, setup notes, logs, and enough context for your team or another developer to extend it.
I use modern AI-assisted development tools where they speed up implementation, research and iteration. I remain responsible for scoping the work, making the technical decisions, reviewing the code, testing the system and delivering something your team can maintain.