ABOUT SLAKE DESIGN · AUSTIN, TX

You work directly with the engineer building your software.

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

Direct collaborationYou work with the person making the technical decisions.
Working software over theaterI use AI-assisted tools to move faster, then validate the implementation against the real workflow: requirements, edge cases, integrations, data behavior, tests, deployment and handoff.
Built for handoffYour team receives the code, context, and documentation to keep moving.

Anish Jhaveri

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.

Solutions & Implementation

I turn a business requirement into a scoped build: the workflow, system boundaries, data involved, risks, milestones and the smallest useful first release.

Full-Stack Development

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.

AI Systems & Automation

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.

Business Systems & Data Workflows

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.

A simple path from uncertainty to owned software.

01

Clarify the constraint

Identify the input, decision points, edge cases, authoritative records, and success metric before talking about a build.

02

Build the smallest useful system

Use deterministic rules, integrations, search, or AI only where they make the workflow easier to run and review.

03

Hand over something maintainable

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.

START WITH A PROJECT

Ready to build or improve your software?