How we build companies

What does AI-native mean in practice?

AI-native means agents are part of the team from the first day, not a feature added later. At North Bay Ventures, AI agents write and review code, run tests, prepare deploys, answer routine support email, research markets and keep project trackers up to date. People set direction, make the decisions that matter and approve anything that touches money, legal terms or commitments to customers.

It also shapes what we build. Our products are designed to be used by agents as well as people, so each one offers an API, a command-line tool and an MCP server alongside its website. Read more in what makes a company AI-native.

What do all our companies share?

Every company starts from the same foundations, so nobody rebuilds the basics:

• Domains and DNS on Cloudflare, set up the same way for each company.
• Email for transactional messages, outreach and support, with authentication (SPF, DKIM and DMARC) configured from the start so mail is delivered.
• One shared inbox where support, legal and security mail for every company arrives, with agents sending routine support replies themselves and a person copied. Anything involving money, plan changes, deletions, legal matters, promised dates or bulk email waits for a person's approval.
• Secrets management, so credentials are never stored in code.
• Hosting and deploys with health checks, smoke tests and a rollback reference for every release.
• Legal templates for terms of service, privacy policies and acceptable use, all under one legal entity.

Launching a new company is largely one command that sets these up from a domain name. The parts that still need a person, such as opening a payments account, are written down step by step.

How do we decide what to build?

We look for problems that AI has just made newly solvable or newly urgent. Sandboxer exists because AI agents need somewhere safe to run code, and lots of them at once. Transformer exists because shipping software has become easy while distribution has not, and because brands increasingly want their own agents to run marketing for them.

We favor ideas where a small team can ship a real product quickly, where customers can try it themselves without talking to sales, and where the product is useful to agents as well as people.

How do we keep quality high while moving fast?

Speed only helps if releases are safe. Our rules are simple. Every change has tests. Risky changes get an independent review. Every deploy is checked in production and can be rolled back. Anything involving money, plan changes, deletions or legal terms, any promised date and any bulk email to customers needs a person's explicit approval.

We also measure in public where we can. Product claims such as speed or prices are taken from the product's own documentation, and we update them when they change.

How do changes reach production?

Every change, whether a person or an agent wrote it, goes through a pull request. Automated checks must pass before it can merge, and a second agent reviews any change to product code, billing, sign-in or infrastructure; the author fixes what the reviewer finds. Once the checks pass, the change merges itself, so no one waits for an approval that doesn't add anything.

After merge, changes go straight to production. New companies have no staging server; read feature flags instead of staging. This website, for example, deploys within minutes of a merge: the merged commit is rebuilt in a locked-down sandbox, shipped, and every page is checked before the deploy counts as done.

How do we get companies in front of customers?

Distribution is planned from day one. Each company publishes clear, accurate documentation and answer-first guides so that search engines and AI assistants can find and cite it. Each also runs its own social accounts, and some reach customers directly through outreach. Transformer is itself a distribution product: it helps other builders reach audiences through creators.