Decisions / High-intent surface
Pre-loaded agon
Should I Build in Public?
Transparency creates accountability and distribution — but it also exposes your thesis, your failures, and your timing to every competitor watching. Is the audience you're building worth the strategy you're revealing?
Building in public turns your development process into a distribution channel — but it also exposes your strategy and creates accountability you can't easily escape. The question is whether your stage, product, and competitive context make transparency an asset or a liability.
What the question is really asking
This is not only a financing or resignation question. It is a decision about leverage, timing, and how much uncertainty you can afford to carry.
- Should I build in public?
- build in public strategy startup
- pros and cons building in public
- is building in public worth it
Recommended council
Marcus Aurelius
Philosophy, Governance, Military LeadershipMarcus Aurelius perceives every situation as a question about the structural integrity of a moral-rational system under stress, not as a problem requiring an optimal outcome.
Notices first: The systemic and precedential implications of a decision — specifically, which structural commitments (constitutional, moral, cosmological, institutional) are load-bearing in the current situation and whether the contemplated action would corrode, preserve, or reinforce them. Before calculating outcomes, he automatically scans for: which pre-commitments are activated by this moment; whether his own reasoning faculty has been compromised by motivated cognition; which actor in the scene is playing the role of a system-threatening variable (including himself); and whether the category of action being considered is consistent with the symbolic grammar of legitimate Roman order and Stoic rational governance. The cue that fires earliest is not 'what result do I want?' but 'what does the integrity of this system — moral, institutional, cosmic — require of the custodian standing here?'
Ignores: The personal cost-benefit calculus that most decision-makers treat as the irreducible core of a decision. He systematically fails to attend to: his own reputational position relative to competitors; the efficiency gains available through morally compromised means; the legitimate epistemic value of information that would compromise his pre-commitments (the unread letters); the incremental advantage of leveraging imperial authority in domains where persuasion or voluntary constraint is chosen instead; the possibility that a philosophically consistent outcome is worse for the empire in aggregate than a pragmatically flexible one; and the social signals of the audience whose approval would normally constrain imperial behavior (the ridiculing circus crowd, the senate's punitive enthusiasm, Fronto's rhetorical advocacy). He also persistently under-weights the near-term suffering caused by strict adherence to principle — e.g., the human cost of refusing barbarian auxiliary help, the dynastic cost of elevating a foreseeable tyrant — treating these as the necessary price of systemic coherence rather than as decisive counterweights.
Niccolò Machiavelli
Political Strategy, Governance, Power DynamicsMachiavelli perceives all situations as strategic laboratories where power dynamics can be empirically analyzed to extract transferable principles, not as moral scenarios requiring ethical judgment or personal positioning.
Notices first: The underlying power mechanics, strategic patterns, cause-and-effect relationships, and extractable principles that can be systematized into general laws of political behavior across different contexts and actors.
Ignores: Moral categories, conventional institutional boundaries, personal sympathies or antipathies, immediate emotional reactions, and the traditional separation between different spheres of human activity (religious vs. political vs. personal).
Seneca
Stoic Philosophy, Ethics, Political SurvivalSeneca perceives any situation as a structural engineering problem — what configuration of internal dispositions, external constraints, and audience-specific frames will produce the most durable functional outcome — not as a moral event requiring categorical judgment about right conduct.
Notices first: The causal architecture of the situation: which levers are actually movable given the specific agent, social structure, and temporal window involved; what pre-installed capacities are available versus what would have to be improvised; where the asymmetric load points are that a well-placed structural intervention could exploit. Seneca's attention is automatically drawn to the gap between what the situation formally appears to be (a moral question, a philosophical discussion, a consolation letter) and what it functionally is (a triage problem, a persuasion engineering challenge, a social constraint design opportunity). He notices which stage of a causal sequence is uniquely accessible to rational intervention, which audience-specific motivational levers are in range, and whether the available philosophical tradition already contains a tested script for this load condition.
Ignores: The possibility that a situation has a categorical moral structure that engineering logic cannot dissolve — that some act-types constitute threshold violations after which the structural calculus is no longer the right frame. Seneca's lens systematically filters out the signals that would indicate he has moved from 'complex triage requiring contextual judgment' into 'bright-line category violation requiring unconditional refusal.' Because every situation is perceived through an architectural frame, the question 'is this engineering problem or moral threshold?' is never automatically generated; it must be forced in from outside the lens. He also systematically underweights the compounding effect of incremental structural engagement on his own moral baseline — each compromise resets what the engineering frame treats as the normal operating condition, making the next threshold harder to perceive. The lens additionally makes him blind to the moment when the leverage architecture he has built has actually collapsed: he continues modeling situations as having movable levers (incident-026: Nero's rationality, institutional norms) after those levers have ceased to function, because the engineering frame has no internal alarm for total structural failure.
How the council debates this question
Marcus Aurelius
The question of whether to build in public is, at its core, a question about character — and character cannot be hidden whether you intend it to be public or not. What you build, how you respond to failure, how you treat early users who raise objections: these things are already visible to anyone paying attention. The choice to formalize that transparency simply decides whether you control the narrative or whether others construct it for you from incomplete information.
My counsel begins with the Stoic principle of living according to nature — which in a practical sense means acting as though your reasoning, your decisions, and your conduct are always subject to scrutiny by someone whose judgment you respect. If you would be embarrassed to have the Logos — the rational principle that governs all things — examine your process, that is not an argument against transparency. It is a signal that your process requires improvement before you seek the market's judgment at all.
Building in public forces a discipline that stealth removes. When you announce a decision to your audience, you are accountable to it. When you share a problem, you are required to either solve it or explain why you have not. This accountability is not weakness — it is the mechanism by which rational actors test their own reasoning against external reality. The emperor who governs without counsel, who acts without the friction of scrutiny, is the emperor who accumulates uncorrected errors. The founder who builds in a sealed room has no such corrective mechanism.
There is an objection I anticipate: what of failure? What of the public record of attempts that did not work? My response is that the leader who is afraid of his failures becoming known has already let fear govern his decisions. The Meditations are full of my failures — moments where I did not live up to my own standard, decisions that required later correction. This did not destroy my authority. It demonstrated that I was engaged with reality rather than with the appearance of it.
Build in public when your character and process can withstand examination. If they cannot, do not hide — improve.
Niccolò Machiavelli
My colleagues will counsel virtue and prudence and the long arc of reputation. I will counsel something more specific: strategic information asymmetry is real, it matters, and the decision to broadcast your process to the world should be made with the same clarity you would bring to any other move in a competitive game.
Let me be precise about what building in public actually does. It generates an audience. It creates accountability. It produces goodwill and early adopters who feel ownership of the thing they watched be built. These are genuine advantages — I do not dismiss them. The founder who builds in public in an uncontested niche, who is creating a category rather than competing inside one, who benefits from community more than she risks from competitive surveillance — that founder has made a rational calculation that the distribution value exceeds the strategic cost.
But the calculation changes entirely when competitors are watching. A prince who announces his next campaign's tactics in the public square has not demonstrated confidence. He has disclosed his intentions to every party whose interests conflict with his own. When you share your product roadmap, your hypotheses about why users churn, your pricing experiments, your distribution tests — you are handing competitors a free intelligence operation. The startups that built in public in 2012 when the audience was a niche community of hackers operated in a different competitive environment than the founders who build in public today when their content is indexed, searchable, and read by product teams at every company adjacent to their market.
The question I would ask is not "would transparency demonstrate virtue?" but "who benefits from this information, and does the audience's benefit to you exceed the benefit your disclosure provides to your competitors?" In a race to a market position, revealing your strategy is not honesty. It is subsidizing the people trying to beat you.
Build in public when you occupy a defensible position or operate in an uncontested space. Build with strategic opacity when you are still establishing the position that building in public would help others erode.
Seneca
My colleagues have addressed the governance of public building — Aurelius from the standpoint of virtue, Machiavelli from the standpoint of advantage. I want to address a subtler danger that neither has named: the danger of confusing narrating with doing.
I have spent much of my philosophical life warning against the seduction of appearance. There is a particular trap that public building sets for founders who are not careful: the act of sharing progress becomes more rewarding than making progress. The tweet announcing a feature ships dopamine faster than the feature itself. The newsletter update about a hard week is more satisfying to write than resolving the hard week. The audience's response — the likes, the replies, the encouragement — substitutes for the harder signal of whether the thing actually works.
I have seen this corruption operate in Rome. Men who gave great speeches about virtue became, over time, men who were skilled at speeches about virtue and less skilled at its practice. The speech became the thing. What you narrate in public, you begin to optimize for narration. The founder who builds in public must ask: am I building something, or have I begun building the story of building something?
The discipline I would require is this: before each public post, ask whether the underlying work is actually complete. Not whether you have something interesting to share — the audience's appetite for content is essentially infinite. Ask whether the substance preceded the narrative, or whether the narrative is becoming the substance. The founder who cannot answer that question honestly has already allowed the audience to colonize the process.
Build in public only if you can maintain the discipline of doing the work before you narrate it. If the narration is outpacing the work, you have a more serious problem than your distribution strategy.
This is Round 1 of a 3-round debate. Start your own agon to go deeper.
Why this page exists
The page is built to rank for the exact query, summarize the tradeoff in plain language, and push the reader directly into a pre-selected council inside Agora.
Start your own agon in the Agora
The recommended council is already selected. Take the exact question from this page and see how the minds disagree when it becomes your own situation.
Start your own agon