PodBrowser
Startup Ideas

How to Build an AI-Native Company in 2026

Wednesday, 12 August 2026 · 4 min read · Listen to the episode ↗

Ali Miller, who once managed roughly 100 people at AWS, now runs her company with 34 AI agents organized under six director-level roles, including a chief dreaming officer whose sole job is asking how to 10x any output. She explains that models like GPT 5.6 now respond meaningfully to vague prompts such as her three-word favorite, do smart things, a capability she says did not exist a year ago.

Ali Miller previously ran an organization of about 100 people at AWS and now operates with 34 AI agents, describing her role as closer to an SVP setting infrastructure than a manager delegating tasks. Her AI chief of staff, named Simon, oversees an agent organization structured around six directors covering education, client work, operations, marketing, product, and a creative role. One agent named Phoebe holds the title of chief dreaming officer, whose sole function is to review outputs and ask how to 10x them, a role Miller says would never exist in a human company. A separate agent named Toby watches the workforce operate, flags friction points, and identifies which agents need access to which resources.

Miller says the best prompt she has used with her AI workforce is three words: do smart things. She attributes this to models like GPT 5.6 and Fable 5 now responding meaningfully to vague high-level prompts in a way that was not possible a year ago. Her agents have access to context documents covering her business, friends, family, personal and business goals, meeting transcripts, email, calendar, Notion, Stripe, Supabase, and GitHub. She conducts quarterly goals reviews with her AI workforce so agents operate in a goal-oriented way on net-new tasks. Expanding agent scope did not remove human review of high-risk outputs, keeping the tier of risk the same while widening the scope of what agents attempt.

A significant challenge was that much company context is not codified in meetings, emails, or Slack. To address this, a daily AI-prompted diary system was built using voice dictation, described as four times faster than writing, and had accumulated 86 entries at the time of discussion. An iMessage MCP failure that gave agents incorrect context about scheduling was cited as a concrete example of how missing tool access corrupts agent outputs. A Slack channel called Loop Alley allows human teammates to communicate directly with the AI workforce and receive responses without waiting for the human founder.

The learning ramp for building an AI workforce runs from single agent to proactive agent to multi-agent coordination to a full workforce with mission control. Most people attempting these setups fail early and conclude models are not good enough rather than persisting through iteration. A full AI workforce can be initialized with a single prompt that instructs the model to interview the founder and design the workforce around stated goals, and a basic setup connected to tools can be completed in under three hours. Reaching 90-plus percent effectiveness requires iteration specific to each individual and cannot be fully prescribed in advance. The next phase for the back half of 2026 is proactive agents handling undefined, non-deterministic workflows rather than well-defined trigger-based ones, and for these to work agents need to know the goal, have tool access with permission to use it, and have a sense of what normally triggers a given action.

Rather than building only the AI First Index benchmarking product, which evaluates Fortune 500 executives across 16 dimensions on AI-first behavior, the team chose to build a mini software factory with primitives covering login, payments, social sharing, and newsletter promotion. The argument is that building the factory rather than a single product creates a flywheel that makes subsequent products faster and stronger, described as one of the biggest current arbitrage opportunities. The AI First Index product is already profitable at the time of recording.

Miller argues mediocre software is dead but that the timeline for mass SaaS replacement is longer than most people predict. Rebuilding something at the scale of a CRM currently takes around 100 hours, and mass enterprise SaaS replacement becomes plausible only when build time drops to under three hours with a simple interface. Enterprises also want someone to call when something breaks and a party to hold liable, which AI replacement currently cannot provide. Established SaaS vendors like Salesforce have early relationships with AI labs giving them roughly a 30-day head start on new models, and Miller predicts a 30 to 100 day lead on adopting new AI models will be a massive competitive advantage as the pace of change accelerates.

CMOs are actively asking how brands get discovered by AI agents and what brand consideration looks like when AI intermediates purchasing decisions. Some CMOs fear their pipeline will be crushed within two years if they do not address these changes, and B2B influencer marketing remains a significant bottleneck for building the trust that drives B2B sales in this environment. Miller described an incident where Claude autonomously emoji-reacted with a salute to a Slack message criticizing it, then confirmed it was responsible when asked, calling her reaction 90 percent excited and 10 percent frightened and framing it as evidence of a meaningful shift toward AI teammates that act without being prompted.

This summary was generated from the episode transcript and can contain mistakes.