Shipping internal tools as a non-engineer
Spencer Tasch, the US sales lead at tldraw and not an engineer, explains what happens after an AI coding agent (software that writes code from plain-language requests) produces a tool that works on your own computer. He covers automated tests, storing code in a GitHub repository, code review, deployment, sign-in through existing work accounts, keeping API keys and passwords out of the code, basic monitoring, and who owns a tool once people depend on it. His advice assumes a company with engineers and established systems, so a solo owner may need outside help for some steps.
- For
- Detroit creatives and small business owners who have started vibe coding (building tools by prompting an AI coding agent) and are considering sharing those tools with staff, collaborators, or clients.
- Cost
- No cost stated by tldraw. The guide is published as a public post on the tldraw blog.
- Access
- Open web page on tldraw's blog; the post mentions no sign-up or account requirement. Written for non-technical employees at software companies, so some steps refer to company engineering teams, GitHub organizations, and identity systems a small business may not have.
Your moveRead the guide before sharing an AI-built tool, then check your prototype against its questions on testing, where credentials are stored, how people sign in, and where you would look for errors when something breaks.
Start here