Aviana Le · Creator + Founder · Building in publicInstagram @avianaleMogul Mastery waitlist

Mogul Maxxing  /  Blog  /  Offer Validation

06 · Offer Validation

Building in public: why I'm building my first offer in the open

Building in public can be a useful way to test an offer, or a slow way to perform progress instead of making it. Here is why I'm choosing to build my first offer in the open, what the research on public commitments actually says (it points in two directions), and the rules I'm setting so the openness stays honest.

By Aviana LeNovember 202618 min read
Woman founder writing in a chocolate leather notebook at a cream desk beside a closed laptop and a ceramic cup, drafting build notes for an offer she is building in public
Building in public starts as a writing habit: what I decided, why, and what I still don't know.

Building in public means sharing the process of building a business or product while it's happening, rather than only after it's finished: the decisions, the questions being tested, the reasoning and the things that change along the way. For a first offer, that's useful mainly for one reason. It puts the idea in front of the people it's meant for early, while it's still cheap to change. It's not a guarantee of anything. Done carelessly, it can turn into announcing plans instead of carrying them out, which is one of the risks the research on public commitments points to.

The short answer

I'm building my first offer in public because I want feedback from the people it's for before I build too much, a visible record that keeps my decisions honest, and a regular habit of reporting progress. The research supports part of that: a 2016 meta-analysis of 138 studies found that monitoring goal progress helped people reach goals, especially when progress was recorded or reported publicly. But other research suggests that announcing an intention, especially one tied to identity, can feel like progress and reduce effort. So the rule I'm following is simple: share progress and decisions, not promises. No invented results, no launch dates before they're real, and nothing that belongs to someone else.

This article follows the tool vs workflow vs business system piece, which ended with a promise to explain why I'm building my first offer in public and what that does and doesn't commit me to. It also builds directly on how to validate an offer before you build it, which set out the validation process I'm using. That article was about the method. This one is about the decision to do it where people can watch.

I want to be clear about what this is. The offer is still in development, and this is not a launch announcement. I'm not going to describe results I don't have, or put a date on something that isn't ready. What I can share is the reasoning, the research I looked at, and the rules I'm holding myself to.

What building in public means, and what it doesn't

The phrase gets used for very different things. For some people it means posting revenue screenshots. For others it means a long thread of wins. Neither is what I mean, and neither is required.

In the way I'm using it, building in public means three things:

  • Showing the decisions. What I chose, what I considered instead, and why. This comes straight from the decision log habit I've written about before.
  • Showing the questions. What I'm testing, what I don't know yet, and what would change my mind.
  • Showing the process honestly. Including the parts that are slow, unclear or that I get wrong.

It doesn't mean sharing everything. It doesn't mean real-time reporting of every number. And it definitely doesn't mean making things sound further along than they are. Transparency at company scale has a few well-known examples. The software company Buffer, for instance, has published its salary formula and team salaries since 2013 and has written openly about the reasons. That's a company-level policy, not a solo founder's build log, but it shows that openness can be a deliberate system with rules rather than a stream of posts.

Building in public is a documentation habit with an audience. The audience is useful. The documentation is what does the work.

Why I'm choosing to build my first offer in the open

I considered building quietly and announcing at the end. There are good arguments for that, and I'll come to them. But for a first offer, four reasons pulled me the other way.

1. Feedback arrives while changes are still cheap

The whole point of offer validation is to learn whether people want something before you spend months building it. Building in public extends that. When the questions I'm testing are visible, the people the offer is for can answer them, push back on them, or tell me I'm solving the wrong problem. A note saying "this isn't what I need" is far more useful before the offer is built than after.

That doesn't mean comments are demand. They aren't. A reply is a signal worth following up, not proof that someone will pay. The validation article covers why views are not demand, and I'm holding onto that distinction tightly.

2. Recorded progress is easier to keep

This is the part with the most research behind it. Benjamin Harkin and colleagues published a meta-analysis in Psychological Bulletin in 2016 that pooled 138 studies with 19,951 participants, all testing interventions that prompted people to monitor their progress toward a goal. They found that monitoring progress improved goal attainment, that more frequent monitoring helped more, and that the effect was larger when progress was physically recorded or reported publicly.

Two cautions. Most of those studies were about health goals, such as diet, exercise or quitting smoking, not building a business. And a meta-analysis tells you about averages across many settings, not what will happen to one founder. Still, the direction is clear enough to design around: a regular, written, visible record of progress seems to help people keep going.

3. A public record keeps decisions honest

When I write down why I made a decision, I have to have a reason. When that reasoning is visible, a weak reason is harder to hide from, including from myself. That's not a research finding so much as a design choice, and it connects to the founder operating system idea that decisions should live in a record rather than in memory. A build log is a decision log that other people can read.

4. The people it's for can see how it's made

Mogul Maxxing is about founders with limited work windows using systems and AI to make that time count. If I'm asking people to trust a program built on those ideas, it seems fair to let them see the ideas being applied, including where they don't work. That's also why this series exists at all: the content creator to founder article argued that content should help you learn what to build, not just grow an audience.

What the research says about going public, and where it pulls the other way

Here's where the confident advice online tends to oversimplify. "Tell people your goals and you'll be accountable" is a common line. There's research that partly supports it, and research that suggests the opposite. Both are worth knowing.

Announcing intentions can feel like progress

Peter Gollwitzer, Paschal Sheeran, Verena Michalski and Andrea Seifert published a set of four studies in Psychological Science in 2009 titled When intentions go public: Does social reality widen the intention-behavior gap? They looked at identity-related goals, such as wanting to become a good lawyer or psychologist. When other people took notice of participants' intentions, participants tended to put in less effort toward them afterward than those whose intentions went unnoticed. The authors' explanation drew on self-completion theory: having others acknowledge your intention can give you a premature sense of already being the kind of person you're aiming to be.

These were small studies with university students, focused specifically on identity goals, and I haven't seen large-scale replications that settle the question either way. So I treat them as a caution, not a law. But the caution is real, and it's the trap building in public is most likely to fall into: posting about the founder you're becoming can quietly stand in for doing the founder's work.

Reporting progress is different from announcing plans

Put the two lines of research side by side and a useful distinction appears. The studies that found benefits were about monitoring and reporting progress toward a goal. The studies that found a cost were about having an intention or identity acknowledged before acting on it. Those are different behaviors, even though both happen in public.

SourceWhat was studiedFindingWhat I take from it
Harkin et al. (2016)Meta-analysis of 138 studies, 19,951 participantsMonitoring progress improved goal attainment; stronger when recorded or reported publiclyShare progress regularly, in writing. Mostly health goals, so the size won't transfer
Gollwitzer et al. (2009)Four studies on identity-related intentionsWhen others noticed an intention, effort toward it droppedDon't announce identity or plans as if they were progress. Small lab studies; treat as a caution
Gilovich, Medvec & Savitsky (2000)Students wearing a conspicuous T-shirt into a roomPeople overestimated how many others noticed themThe fear of being watched is usually bigger than the attention. Lab setting

That's why my rule is to share progress and decisions, not promises. "This week I spoke to people about X and here's what changed" is a progress report. "I'm going to build the best program for founders" is an identity announcement. The first one seems to help. The second one may quietly replace the work.

The fear of being watched is usually larger than the watching

A common reason founders give for avoiding building in public is worry about looking foolish if something doesn't work. That's a reasonable concern. It's also, on average, overestimated.

Thomas Gilovich, Victoria Medvec and Kenneth Savitsky described the spotlight effect in the Journal of Personality and Social Psychology in 2000. In one study, students were asked to wear a T-shirt with a famous singer's face on it, chosen to be mildly embarrassing, into a room of peers. They estimated that about half the people in the room would notice. In fact, closer to a quarter did. Across their studies, people consistently overestimated how much others noticed their appearance and actions.

This was done with students in a lab, and an online audience isn't the same as a room. But it fits the experience most people describe once they start: the attention is real but thinner than feared, and it's mostly from people who are interested in the same problem. That's exactly the audience a first offer needs to hear from.

What I will share, and what I won't

Openness without rules drifts toward whatever gets the most reaction. So I wrote down what goes in the build notes and what stays out. These are the boundaries I'm working with.

I'll shareI won't share
The problem the offer is meant to solve, and who it's forResults I don't have, or numbers I haven't measured
The questions I'm testing and what would change my mindLaunch dates before they're decided and ready
Decisions and the reasons behind themAnyone's private messages, names or details without permission
What changed after conversations, in general termsTestimonials, quotes or stories that aren't real
Process mistakes and what I'm adjustingFeatures or promises the offer can't yet keep
The research I'm using, including where it's contestedClaims that the method is proven

The right-hand column matters more than the left. Most of the damage done by building in public comes from things people share that weren't true yet: a result rounded up, a date announced early, a feature described before it existed. Each one is small. Together they turn a build log into marketing, and the audience can usually tell.

My rules for building an offer in public

Five rules for building in public honestly

1. Report progress, not promises. Share what happened and what I decided, not what I'm about to become.
2. Separate what I know from what I'm guessing. Every build note says which is which.
3. No dates until they're real. "In development" is an honest status. A date that slips is not.
4. Privacy for anyone who replies. People who share their problems with me are helping, not providing content.
5. Say what changed and why. If a decision reverses, the reversal and its reason go in the log too.

These rules are part of the system, not just intentions. In the language of the tool vs workflow vs business system article, building in public only works if it has a trigger (a set day for build notes), an owner (me), a definition of done (a short note covering decisions, questions and changes) and a review (checking each note against the five rules before it goes out).

Mogul Mastery · founding waitlist

Watch the offer being built, and help shape it

Mogul Mastery is the implementation program I'm building in public for founders with limited work windows: decision rules, operating rhythms and AI used for context and decision support, set up around your own business. It's in development and shaped by the people on the founding waitlist.

Overhead view of a cream linen desk with an open notebook of handwritten lines, a short stack of index cards held with a brass clip, a pen and a ceramic cup, a founder planning weekly build notes for an offer
A build note covers three things: what I decided, what I'm testing, and what changed.

How to build your own first offer in public

If you're considering the same approach, this is the process I'm following. It's deliberately small, and it fits inside limited work windows.

1. Decide what the openness is for

Write one sentence: "I'm building in public so that ___." Feedback from the right people, a record that keeps me consistent, trust with a future audience. If you can't finish the sentence, the openness will drift toward attention for its own sake.

2. Write your share and don't-share lists first

Before you post anything, decide what stays private. Numbers you haven't measured, other people's details and dates you haven't committed to are good starting points. It's much easier to set the boundary before the first post than after an awkward one.

3. Make the build note a fixed slot in your week

A regular rhythm beats posting when inspiration strikes. Once a week is plenty. The note can come straight from your weekly review: what did I decide, what am I testing, what changed? If you use the 60-minute work window plan, the last ten minutes of one session can produce it.

4. Ask one specific question each time

"Thoughts?" gets little back. "If you run two businesses, what's the first thing you drop when a week goes wrong?" gets answers you can use. The questions should come from your validation plan, so the replies feed the decision you actually need to make. The multifaceted entrepreneur article is a good example of the kind of specific problem worth asking about.

5. Follow up privately with the people who reply

Public replies are a starting point. The useful learning usually happens in a short conversation afterward, where someone can describe their situation properly. That's where a comment can become a validation interview, and possibly a real signal of demand.

6. Review the log, not the reactions

At your weekly review, look at what you decided and learned, not at how many people liked the post. Reactions measure reach. The log measures progress. If they disagree, trust the log.

The real risks of building in public

I don't think building in public is right for everyone, or for every stage. These are the risks I'm watching for in my own build.

  • Performing instead of building. The Gollwitzer research is the clearest warning here. If posting about the work starts to feel like the work, that's the moment to post less.
  • Mistaking attention for demand. Likes and replies are easy to count and tempting to read as validation. They aren't the same as someone paying, or committing to try the offer.
  • Survivorship bias in the stories you read. Most build-in-public stories that get shared widely are the ones that worked. The ones that didn't rarely trend. That makes the approach look more reliable than it may be.
  • Time cost. Writing build notes takes time out of a limited work window. If it's taking more than a small slice of the week, the format is too heavy.
  • Someone copying the idea. It can happen. In practice, for most first offers, the idea is rarely the hard part. Understanding the people it's for, and earning their trust, is much harder to copy. If the idea really does depend on secrecy, building in public may not be the right choice for it.
  • Locking yourself in. Public reasoning can make it feel harder to change direction. The fifth rule above exists for this: a visible reversal, with its reason, is a sign the process is working.

Where AI fits in a build-in-public routine

AI is useful here in the same limited way it's useful elsewhere in this series. It can turn a week of decision log entries into a first draft of a build note, check a draft against the five rules, or pull out the questions that came up most often in replies. That saves time inside a short work window.

What it shouldn't do is write the reasoning, invent detail to make a note more interesting, or decide what's ready to share. Those are judgment calls, and the AI second brain for founders article explains why I keep judgment with a person. The same goes for the AI second brain more generally: the assistant can hold context and draft, but the decisions stay mine. And if you're unsure whether the build note or the build itself should get your next hour, the rules in how to decide what to work on first apply. The build usually wins.

Build-in-public taskGood AI roleKeep human
Weekly build noteFirst draft from the decision logThe reasoning and the final edit
Checking honestyFlagging anything that sounds like a promise or a resultDeciding what's true and ready to share
Reading repliesGrouping recurring questionsChoosing who to follow up with, and how
Validation questionsSuggesting clearer wordingDeciding which question matters this week
Woman founder in a camel knit sweater at a long cream table in a warm studio, reading printed notes and marking them with a pen in late afternoon light during a weekly review of her build log
Review the log, not the reactions. The log is what shows whether the build is moving.

Frequently asked questions

What does building in public mean?

Building in public means sharing the process of building a business or product while it is happening: the decisions, the questions being tested, the reasoning and what changes along the way. It does not require sharing every number or every detail, and it works best with clear rules about what stays private.

Is building in public a good idea for a first offer?

It can be, mainly because it brings feedback from the people the offer is for while the offer is still easy to change. It is less useful if the idea depends on secrecy, or if posting starts to replace the actual work. Replies and attention are signals worth following up, not proof of demand.

Does telling people your goals make you more likely to achieve them?

The research points in two directions. A 2016 meta-analysis of 138 studies found that monitoring progress helped people reach goals, especially when progress was recorded or reported publicly. But 2009 studies by Gollwitzer and colleagues found that when others noticed people's identity-related intentions, those people tended to put in less effort. Reporting progress seems to help; announcing intentions may not.

What should you not share when building in public?

Avoid sharing results you have not measured, launch dates you have not committed to, other people's private messages or details without permission, testimonials that are not real, and features the offer cannot yet deliver. Most problems with building in public come from sharing things that were not true yet.

Will someone steal my idea if I build in public?

It is possible. For most first offers, though, the idea is rarely the hard part. Understanding the people it is for and earning their trust is much harder to copy. If an idea truly depends on secrecy, building it quietly may be the better choice.

How often should you post build updates?

A fixed weekly slot works well for most founders with limited time. A short note covering what you decided, what you are testing and what changed is enough. Posting more often adds time cost and can drift toward performing progress rather than making it.

Are comments and likes evidence that people want the offer?

No. They show interest or reach, which is useful for finding people to talk to. Demand is shown by stronger commitments, such as someone agreeing to a conversation about their problem, joining a waitlist with a clear description, or paying for a small first version.

Is the fear of looking foolish in public justified?

It is understandable, but research on the spotlight effect suggests people usually overestimate how much others notice them. In a 2000 study, students wearing an embarrassing T-shirt expected about half the room to notice, while far fewer actually did. The studies were in a lab, but the pattern has been found repeatedly.

Can AI help with building in public?

Yes, for limited jobs: drafting a build note from your decision log, flagging anything that sounds like a promise or an unmeasured result, and grouping recurring questions from replies. The reasoning, the final edit and the decision about what is ready to share should stay with you.

Where this goes next

This article sits in the offer validation theme that started with how to validate an offer before you build it. That piece set out the method; this one explains why I'm running it in the open, and the rules that keep the openness honest. It also leans on the tool vs workflow vs business system framework, because a build-in-public habit only lasts if it's a system rather than a mood. Next in the series, I'll go deeper into the question every public build runs into: if views are not demand, what should you track instead?

To get each new article as it's published, join the Mogul Movement. If you'd like to see the offer take shape, and help decide what it becomes, the Mogul Mastery founding waitlist is open. You can browse every article on the Mogul Maxxing blog, or go back to the homepage for the full series.

Sources

This article is general information about research on goals, public commitments and social judgment, not professional or business advice. Study findings describe averages in specific settings, often with students or health goals, and may not apply the same way to every founder. The approach described is being tested in an ongoing build and is not presented as a proven method. The offer mentioned is in development; no launch date has been set.