Before Tim Krug could sell a different way of working, his team needed a different name. The company was called Noodle.ai. The leadership had changed, the strategy had changed, and the name still sounded rather pleased to be experimenting. So the team enlisted ChatGPT, Claude, Google and GoDaddy. Weeks passed. Ideas multiplied. Agreement proved less obliging.
Eventually they hired Lexicon Branding. Krug later described the decision with the appealingly unceremonious ambition to “maintain our sanity.” The process took two months and produced Daybreak. Here was an AI business discovering, in a very ordinary management task, that access to more answers does not automatically produce a decision.
That small episode is a useful entrance to Krug’s larger preoccupation. He now runs a company built around the work between a prediction and an action. A forecast can be calculated. Somebody still has to decide whether to believe it, change it, or commit money against it. Krug has spent his recent career asking what happens when that somebody becomes the constraint.
The salesman who stayed with the problem
Krug’s route into this argument ran through selling enterprise technology. He attended the University of Iowa from 2001 to 2005, studying political science. His early working years included sales management in telecommunications. In September 2009 he joined Kinaxis, where he stayed until November 2018, before moving to Medallia as a sales director.
These were substantial stretches inside businesses whose products had to survive contact with customers. The dates matter more than an origin myth: roughly nine years at Kinaxis, then more than four at Medallia. His career gives the present argument a specific setting. Enterprise buying, deployment and the relationship after the contract are familiar territory.
There is a pleasing tension here. A founder now urging companies to question their inherited software habits spent years working inside the enterprise software economy. The argument comes from someone acquainted with its rituals. A purchase can have a budget, a rollout and a successful launch while leaving the awkward part of the customer’s working day intact.
In March 2023, Krug became chief revenue officer at the business now known as Daybreak. The presidency followed in June 2024. The change of name belonged to that period of new leadership and a revised direction. By February 2026 he was CEO. The progression moved him from selling the proposition toward responsibility for whether the entire operation could deliver it.
A promotion with the work already attached
Daybreak announced Krug’s promotion on February 5, 2026, alongside completion of its Series A financing led by TPG Growth and Dell Technologies Capital. Stephen Collins moved from CEO to executive chair. Krug described the preceding two years as work alongside customers putting AI planning decisions into production. His stated priority was execution.
The company had already announced a $15 million Series A investment in June 2025. The later completion announcement did not supply an amount. Those are two dated announcements, rather than an invitation to add the figures together. For Krug, their relevance is practical: financing supports the effort to put the operating model into more enterprises.
His ambition also has a less corporate expression. In 2025 he described wanting to return time to people, improve business economics and reduce waste. These aims connect the planner’s desk to what happens in a warehouse. Inventory decisions eventually occupy space and tie up cash. A forecast has consequences beyond the attractiveness of its chart.
The number has a biography
Krug’s writing repeatedly returns to a modest incident: someone changes a forecast. The new number is recorded. The explanation often disappears. Perhaps a customer said something on a call. Perhaps a supplier’s behavior recalled an earlier problem. The person has supplied experience the software did not possess, but the system retains only the edited cell.
His July 2026 essay about recording numbers and losing reasons treats that disappearance as wasted knowledge. The experienced planner’s contribution could become something the organization can examine and learn from. Instead, it risks expiring with the individual intervention. The next cycle arrives, and the same person may have to explain the same situation again.
This is where his view of human expertise becomes more interesting than a general promise of automation. The experience matters enough to preserve. He wants the rationale captured when the intervention happens, then compared with the eventual outcome. That would give an organization a way to distinguish an insightful correction from a familiar habit.

He takes the argument upstream in another July essay. A sales history might show what sold without explaining why: a stockout, a promotion, or an unusual purchase can distort what the next forecast learns. His proposed human contribution is to label those circumstances. The intervention then changes the interpretation of the past that feeds future predictions.
That is an exacting request to make of an organization. Changing today’s number is visible and immediate. Explaining an old anomaly is quieter work. Krug’s attention settles on the quieter task because, in his account, it can spare people from repeatedly patching the same downstream answer. The appeal is less typing tomorrow, purchased with more explanation today.
A political scientist’s subject returns
In his essay about politics in demand planning, Krug describes forecast adjustments made to fit an organizational promise rather than a changed market. It is his critique of a management practice, and a revealing choice of subject for someone who studied political science. Authority, incentives and the record of who asked for what all enter the picture.
The remedy he advocates is procedural: attach an owner and a reason to each change. A target and a prediction might look identical in a cell while representing quite different judgments. Writing down the explanation makes that difference available for examination. The spreadsheet acquires something closer to a witness statement.
The same concern appears in his distinction between a plan and the decisions made after it. A plan records agreed intent at a particular moment. Actual operations consist of actions taken as circumstances develop. His attention goes to those events, including departures from the original plan that may have been sensible. A monthly review can admire the destination while missing the turns.
Read together, the essays show the consistency of his public argument. He keeps asking who made the call, what they knew, and what followed. The questions fit a human manager as readily as an AI agent. Giving a machine authority makes the questions more urgent; it does not make them disappear.
The new colleague needs a job description
Krug’s preferred analogy for adopting AI is onboarding a colleague. In his July essay on the subject, a new hire begins with limited responsibilities and close review. Authority grows as performance earns confidence. He argues that companies should put comparable effort into defining what an agent may decide, when it must ask for help, and how its work will be judged.
The analogy is useful because it makes management unavoidable. An installation has a completion date. A colleague continues to require direction. Someone has to own the boundary between routine work and an exception. Krug’s pitch therefore asks customers to do organizational work alongside technical work, including deciding which responsibilities they are prepared to hand over.
“And autonomy should be earned.”Tim Krug, on governing AI decisions
Daybreak describes four stages for that handover: Train, Shadow, Supervise and Delegate. The authority is scoped, can increase with evidence, and can be reduced. The company’s model keeps people responsible for policy and risk while agents take on defined planning work. The vocabulary resembles a careful manager’s notebook more than a switch marked automatic.
- 01Train
- 02Shadow
- 03Supervise
- 04Delegate
Daybreak’s published operating model. Scope and supervision remain adjustable.
In August, Krug widened the frame further. His essay on the company as a decision system asks why existing processes exist at all. An approval may be the residue of an old error. A meeting may compensate for an unresolved disagreement. Adding AI to that arrangement can preserve all its administrative history. His proposal is to examine the decision before improving the machinery around it.
Fifty seats, then dinner and magic
On September 16, 2026, Daybreak held its AI Labor Summit at Soho House Nashville. Krug’s sessions covered the direction of knowledge work, a hands-on personal AI operating system and changes to the organization chart. The program put his managerial argument into a room with people expected to apply it.
The registration offered 50 seats for supply chain leaders. Sessions involved Daybreak, Trillium and Accenture, with customer perspectives from Dot Foods and SharkNinja in the published program. The day’s promised ending was dinner and a private magic show at House of Cards. Even an event devoted to accountable decisions allowed a little room for misdirection after hours.
The hands-on session is a telling detail. Krug was asking executives to consider delegation at their own desks as well as across a planning function. The question becomes personal quickly: which task would you entrust to an agent tomorrow, and what would you need to see before trusting it again?
That brings the story back to the naming exercise. His team had plenty of suggestions and still needed to decide how the work should be done. Hiring help was itself a useful decision. Krug’s current business asks enterprises to make many more such calls explicitly. The ordinary management question underneath his AI argument is stubbornly durable: who owns this, and why?