Unclear problems. No obvious answer. I work out what should exist, then build it.

Engineering decision

Zoho CRM stayed the system of record rather than being replaced, so the platform was built to synchronize against it in both directions instead of holding its own copy of the truth.

Built and integrated

• Operations platform spanning quotes, purchase orders, accounts, and price lists
• Bidirectional synchronization with Zoho CRM objects and workflow rules
• Appwrite holding pricing, quote and document sections, and Discount From Invoice data
• Customer portals with role-specific permissions

Stack

• Nuxt
• Nitro
• TypeScript
• Zoho CRM API
• Appwrite

Engineering decision

The agent proposes and a person publishes. The write interface it is handed has no update, replace, or delete operation, so overwriting something the client entered is not an action available to it rather than a rule it is asked to follow.

Built and integrated

• Scheduled agent running a language model with web search against a strict tool schema
• Structured output filed into the CMS as suggestions, never as published content
• Create-only write surface, so client-entered fields cannot be overwritten
• Human review and approval before anything reaches the live site

Stack

• TypeScript
• Anthropic API
• Tool use
• Structured output

Engineering decision

A model reading a PDF is not evidence. The identifier it proposes is checked against authoritative records before anyone is approved, so the model can make the work faster but cannot be the thing that grants the outcome.

Built and integrated

• Vision-model read of uploaded documentation, proposing an identifier
• Validation of that identifier against authoritative public records
• Approval path that treats the model as a suggestion and the record as the decision

Stack

• TypeScript
• Vision model
• Public records API

Engineering decision

There was no access to the customer’s upstream systems, so the adapter was built against the published event contract alone rather than reaching into anything.

Built and integrated

• Webhook adapter receiving enterprise user and store updates
• Persistence into MySQL through Drizzle ORM
• Authentication integration with the existing enterprise environment
• Operational logging and exportable error reporting

Stack

• Nuxt
• Nitro
• Drizzle ORM
• MySQL
• TypeScript

Engineering decision

A lead has to reach two systems, so a retry after a partial failure must not repeat the half that already worked. Each delivery is claimed in the database before anything is sent, and a target already recorded as delivered is never sent again.

Built and integrated

• Lead-capture integrations with FieldRoutes and Quo
• Claim before send, so a retry cannot create a second customer in a system that already accepted one
• Automatic retry handling for failed deliveries, limited to the failures worth retrying
• Monitoring and failure alerts on lead delivery

Production reality

One target stopped answering rather than failing. Requests hung instead of erroring, the attempts outlived the scheduled worker, and it was killed mid-flight with the delivery still claimed. Every attempt now carries its own timeout and the attempts share a deadline, so a target that never answers costs bounded time and the caller always gets an outcome it can record.

Stack

• Nitro
• TypeScript
• REST APIs

Engineering decision

Counties publish their records in inconsistent formats, so the pipeline normalizes what it receives rather than assuming a single schema.

Built and integrated

• Automated map generation driven by live county records
• Data normalization across inconsistent source formats

Stack

• Nuxt
• Nitro
• TypeScript