I build AI agents that do useful work in production: research, document operations, support workflows, internal tooling, and multi-step actions with clear failure modes. The focus is not on demos. The focus is reliability, observability, and operating cost.
Good fit if
- Founders building an AI-native product that needs more than a single prompt wrapper.
- Teams replacing manual operations with multi-step agents that call tools, fetch data, and write outputs.
OpenAILangChainLangGraphFastAPINext.js
When an LLM needs to answer from documents, product data, or internal knowledge, the quality of retrieval and response policy matters more than model hype. I build grounded systems that can explain what they used, refuse when context is weak, and stay maintainable as the corpus grows.
Good fit if
- Teams shipping support, research, or knowledge workflows where citations and grounded answers matter.
- Products with document ingestion, chunking, embeddings, vector storage, and retrieval debugging requirements.
OpenAIQdrantpgvectorLangChainTypeScript
I work on Web3 products where onchain logic changes how the system behaves and what users can trust. That includes escrow, token operations, smart accounts, settlement flows, and the offchain systems around them: APIs, operator tooling, audit trails, and execution workflows.
Good fit if
- Teams building escrow, token, DeFi, or operator-driven Web3 products with real business rules.
- Founders who need backend and contract logic to move together cleanly instead of being developed in isolation.
SolidityFoundryHardhatEthereumBase
Payments are where weak backend design becomes expensive. I build Stripe-backed systems with the boring but necessary pieces done correctly: retries, idempotency, webhooks, reconciliation, operator visibility, and product flows that do not fall apart once real money is involved.
Good fit if
- SaaS teams launching subscriptions, invoicing, or account lifecycle flows.
- Marketplace or operator products using Stripe Connect and payout orchestration.
StripeNode.jsNestJSNext.jsRedis
I work best on products with moving parts: frontend, backend, automation, payments, data, and AI features that all need to cooperate. The goal is not to ship fast at any cost. It is to ship ambitious products cleanly, with architecture that still makes sense six months later.
Good fit if
- Founders who need one engineer who can reason across product, architecture, delivery, and implementation.
- Small teams that need backend-heavy delivery without losing frontend quality.
Next.jsTypeScriptNode.jsNestJSFastAPI