Building @tempo_labs (YC S23) | Forbes 30 u 30 | Prev $100M+ exit @PerpetuaLabs. On a mission to help teams ship software to production 10X faster.

Toronto, Ontario
Joined June 2011
Today we're launching @Tempo_Labs — the everything app for product teams. Think Linear + Figma + Notion, rebuilt around your codebase and your coding agent (claude code, codex, or opencode). Here's what's shipping today 👇
26
25
6
124
23,473
Why did they feel the need to do @cohere dirty like that
microagi just crossed $100M in 6 months. Faster than Lovable, OpenAI, Cursor, Wiz, and every software company in history. We are living through an unusual moment where physical companies are starting to scale as fast as software companies. Huge thank you to everyone who made this possible! <3
1
4
398
Kevin Michael retweeted
convergence to the mean when everyone looks at everyone else to decide what to make, we eventually stop making anything of our own. we copy what works. borrow the language, the aesthetic, the features. we call it learning from the market, following best practices, staying competitive. together, everything starts to feel familiar. polished, interchangeable. nothing wrong. nothing alive. the mean isn’t necessarily bad. it’s where everything lands when we remove the reasons for it to be different. numbers are easier to compare than feelings, so we make things that produce numbers. we study what gets attention, then shape ourselves around it. eventually the feedback stops informing the work and starts authoring it. we’re no longer asking what we want to say. we’re asking what will be rewarded for saying. ai makes this loop frictionless. it can draw from more references than we could see in a lifetime. but access to every perspective isn’t the same as having one. it hasn’t lived a particular life that makes one detail unbearable and another beautiful. when we ask it to choose for us without bringing any intention of our own, we get something plausible, easy to approve. then we ship it, measure it, copy it, and feed it back into the next round. a tidal wave of mid. this changes not just the work, but the people making it. we describe ourselves in categories platforms can distribute and markets understand. designer. founder. creator. pick a niche. build a brand. be consistent. the parts that don’t fit become inconvenient, even when those contradictions might produce our most interesting work. we become easier to classify and harder to tell apart. i think we need to approach making things more like artists. an artist develops a perspective through the work. making, noticing, choosing, failing, returning. learning what matters even when nobody else cares. craft gives that perspective a form precise enough for someone else to experience. the life outside the work matters too. the places you’ve lived, the people you’ve loved, the things you’re embarrassed to care about. these aren’t distractions from having something to say. they’re how you come to have something to say. we understand this with music, paintings, photographs, movies. we expect a person to be present in the choices. we want to experience something we wouldn’t have encountered without them. software can do this too. a piece of software expresses beliefs about how life should feel. what deserves your attention. what you should be free to change. whether a task should feel like paperwork or play. even a small interaction can carry someone’s care, humor, or curiosity. but we rarely talk about software as a medium. we talk about it as an industry. markets to capture, workflows to optimize, competitors to catch up with. we add a feature because someone else has it, without asking whether it belongs. products accumulate the same parts and lose what made them worth choosing. underneath the branding, it’s all the same thing. artists learn from others too. the question is whether you’re absorbing those influences into a point of view, or using them to avoid developing one. what are you trying to let someone feel, understand, or do? why this particular shape? what have you noticed that the existing tools don’t seem to notice? those questions don’t have answers you can borrow from a competitor’s roadmap. if we can make almost anything, deciding what deserves to exist becomes more important, not less. speed gives us more chances to exercise judgment. it doesn’t remove the responsibility. i don’t want a world where every person becomes a more efficient distributor of the same ideas. i want people to use these tools to go further into what they actually care about. to make things specific enough that we can feel someone behind them. what is the point of everyone being able to make something, if we all end up making the same thing?
131
355
153
2,699
312,669
Kevin Michael retweeted
Your design system is already in your codebase. Tempo can pull your existing components and styles onto the canvas, giving you a visual design system based on what’s actually in production. No need to recreate everything from scratch.
2
13
920
Kevin Michael retweeted
Bring any website onto Tempo’s canvas and start editing
1
15
1,214
Need to try this haha
best thing my wife and I implemented with kid in the picture is a 1h weekly meeting during work hours for “life ops” then life ops doesn’t cast a shadow over the weekends and weekday evenings where little compute is left
2
274
So sick @sparkmark_ !
what if controlling your agents felt like orchestrating them? design, interactions, animations, all made in code with @Tempo_Labs
1
3
333
Loved reading this. Articulates the feelings we've been having that PRs should be larger in general. Human review is the bottleneck so the less rounds of review the farther you can get. Classic min flow max cut problem.
At @11x_official , we’re trying to one-shot entire software builds. It’s a play on one-shot prompting, applied to the build itself: we hand an agent a detailed spec and let it work through the implementation, tests, and fixes in one autonomous run before coming back to us for review. That’s making us rethink how we build software. We’re putting more work into the spec up front and giving agents larger builds, with fewer human handoffs along the way. To make that possible, we started an AI-native codebase. Our engineers encode what they know about building good software into guardrails, checks, and tests that agents can use to continuously verify their own work. The idea is to give AI more autonomy while maintaining control over how the software is built. We recently rebuilt a core 11x product feature in one week. The original took three months. The rebuild included a 15-hour autonomous run. Of the six days of human work that week, four went into discovery and writing the spec — before any code was written. We’re still early, but it’s changing how we think about the role of an engineer, how we structure our codebases, and even whether breaking projects into smaller tickets is always the right approach. I wrote about what we’re learning in “One shot,” the first post on our new 11x Engineering Substack: 11xengineering.substack.com/…
1
1
263
Kevin Michael retweeted
These are metrics from Agent+, the software development service we run alongside Tempo. Without adding a single engineer, our output has nearly doubled. Here's what changed:
1
2
6
596
Kevin Michael retweeted
Tempo is super helpful.
1
2
2
148
Kevin Michael retweeted
Replying to @saurra3h
You could also use Tempo to design with code :)
2
2
6
248
Kevin Michael retweeted
Don’t get so caught up trying to give your kid a good life that you forget to give them a good day
65
926
38
18,809
225,310
🤤
imagine a software factory powered by GPT-6 Astra
1
8
625
Many such cases
My longest client just stopped service after 1.5 years on our highest tier. Their PM started vibe-coding with AI. She'd propose AI solutions first, then ask designers to improve later. AI sped everything up so much that design became the thing everyone was waiting on. We went from partner to blocker. I'm not mad. I'm paying attention.
1
354
Kevin Michael retweeted
Fable 5.1 is now available in Tempo
1
4
11
938
Kevin Michael retweeted
companies will yap about having taste/unique brand image then proceed to use the same 3 design agencies as everyone else
2
1
1
18
1,848
Hope is a primary virtue.
If you want your company to be gritty: create a gritty culture, hire gritty people, and celebrate gritty achievements.
1
4
323
good take :)
“software factory” is a stupid term - the whole point of factories is to make lots of the same thing, and software is already infinitely replicable what you want is a software studio - make it dramatically easier to design, craft, maintain, evolve, and debug - not blind automation but increased visibility
1
3
376
Kevin Michael retweeted
Darren went from shipping 1–3 features a week to 1–3 features a day And he was already using Claude Code So how did Tempo 5× his output? He walks through exactly what changed
1
2
9
721
Kevin Michael retweeted
What if your agents worked on your backlog without being prompted? With Tempo Software Factory: A ticket comes in, and the agents automatically get to work.
1
3
10
1,507
Its been a wild few weeks
In June, we launched Custom Agents internally, transforming Tempo from a developer tool into a software factory. Since then, we’ve doubled merged PRs/week from ~90 to ~200 — and velocity is still accelerating. See what we’re shipping and how fast we're shipping it: tempo.new/progress
8
536