a chatbot is a text box wired to an api key. an agent is a system: it holds state across steps, decides which tool to call and when, retries when a call fails, and stops itself when it is about to do something it should not. the gap between a claude prompt in a demo and an agent running inside a production next.js app is the same gap between a spreadsheet macro and an actual backend service. an autonomous support agent that reads a ticket, checks three internal systems and drafts a reply a human approves in ten seconds instead of ten minutes. a document-processing pipeline that ingests thai and english invoices, extracts line items with a retrieval layer over your own product catalog, and writes structured rows to postgres with a confidence score attached. a research agent that runs six searches, cross-checks sources and returns a memo instead of a wall of links. that is the shape of work that lives in this service.
prompt engineering gets a demo to work once. software engineering gets it to work the four-hundredth time, at 2am, when the upstream api times out and the agent has to retry with backoff instead of inventing an answer and shipping it to a customer. that is why this work sits with senior engineers, not prompt specialists: the hard part is the state machine that tracks where an agent is inside a multi-step task, the tool-use layer that gives claude a typed, permissioned surface instead of raw api keys, the eval suite that catches a regression before a client does, and the guardrails that stop an agent from taking an action it was never authorized to take. anthropic's tool-use apis handle the model-calling part well. the engineering around that call, memory design, retry logic, cost controls, evals, is what decides whether an agent ships or gets pulled after week two.
shipped into your codebase, not ours. same discipline as our custom apps service: the agent lives inside your next.js and supabase codebase, github repo under your org from the first commit, supabase project under your billing, claude usage on your own anthropic console. if you already run an internal tool on next.js and supabase, we add the agentic layer to that codebase directly, auto-triage on a support queue, auto-draft on a document type, auto-reconcile on a finance export, instead of rebuilding the platform around a bolt-on tool.
most 'ai automation' pitches in bangkok in 2026 are a zapier or make.com flow with a claude or gpt node stitched in: no state, no memory, no eval suite, no ownership, and no real answer for what happens when the flow hits an edge case at 3am. that is fine for a one-off internal automation. it is not a foundation for a product feature a paying customer touches. agentic engineering is the software-engineering version, the same architecture rigor as a payment flow or an auth system, because an agent that reads customer data, drafts customer-facing replies or triggers a refund is exactly that kind of surface, not a workflow toy.
the engagement starts with a paid technical discovery, not a free strategy call and not a refundable scoping gimmick like claudekick's. discovery produces a written architecture spec (state model, tool inventory, memory strategy, failure modes) and an eval plan (the concrete test cases and pass thresholds the build gets measured against) before a line of the agent loop gets written. that document is yours whether or not you build with us.