
Founder Journal · November 15, 2026 · Nikita Khandheria · 4 min read
An early booking can do more than one job for a young business. It can help support the immediate operation. It can also demonstrate a kind of work the company wants to do more of. Those jobs can overlap, but I have learned that it is worth naming them separately.
In a conversation about ERIA's early growth, I described taking some work because it helped sustain the business and approaching another significant project as an opportunity to demonstrate what we could create. I was thinking about both the present operation and the company I wanted to build.
The useful lesson is not that a founder should work without a margin or treat exposure as payment. It is that a project should have an understood purpose. Otherwise, you can finish an exhausting job and discover that you never agreed with yourself about what would have made it worthwhile.
Immediate contribution deserves respect
There can be a tendency to romanticize the projects that look most impressive and overlook the work that keeps a company functioning. I think that is a mistake. A business needs ordinary commercial discipline as well as ambition.
An event does not have to become the defining image of a brand to be worth doing well. It may serve a clear client need, fit the operation, and make a useful contribution. Those are substantial reasons to take the work seriously.
The important part is understanding the scope and delivering what was agreed. A client whose event serves an immediate commercial purpose for the business is still entitled to care, attention, and a good experience. Internal decisions about the portfolio should never become a hierarchy of how respectfully people are treated.
I also think founders need to be honest about constraints. If a project requires far more work than its commercial terms can support, calling it a useful booking does not resolve the mismatch. The offer, the scope, or the decision to accept it may need more thought.
Demonstration work needs a precise reason
Sometimes a business wants to show that it can deliver a different level or type of work. A project may offer the chance to build that evidence. The value could lie in the work itself, what the team learns, or the way future clients can understand the company's capabilities.
That rationale should be specific. I would want to know what we expect the project to demonstrate and why it is a credible way to do so. A vague promise that it will be good for the brand is not enough. Almost any exciting request can be dressed in that language.
The operational demands still matter. A beautiful outcome that leaves the company unable to meet its other commitments is not a sound foundation for growth. Nor should the team be asked to absorb unlimited extra work because the project has been given an aspirational label.
There is also a difference between learning and assuming. A demonstration project can help us understand what delivering a particular experience actually requires. That knowledge should inform future decisions. The purpose is weakened if we ignore the practical lessons because we are too pleased with the photographs.
Review the project against its actual purpose
After an event, the question should match the reason for taking it. If the purpose was immediate contribution, we should understand whether the work supported that aim after the real effort and costs were considered. If the purpose included demonstrating capability, we should examine what evidence and learning it produced.
That does not require reducing every benefit to one number. It requires enough clarity to learn from the decision. A project that succeeded in one way may have disappointed in another. Both observations can be true and useful.
Our portfolio makes the visible side of the work available to prospective clients. Behind those images are commercial choices about which projects to pursue, how to define them, and what the company can responsibly commit to delivering.
I am interested in building a business with enough stability to keep developing its work. That means respecting projects that support the present while making thoughtful room for the work that helps shape the future.
An early booking becomes more useful when you can say why you accepted it, what you promised, and what you learned. The goal is not to assign every project a glamorous story. It is to make choices you understand well enough to repeat, improve, or decline the next time an opportunity arrives.
Explore all planning guides → Sausalito celebrations →
Plan With ERIA
Ready to bring this to life?
Tell us what you are planning. Our team will help you shape the experience from first idea to final detail.
Start a Conversation
