Open-source the SDK?
Work · Board of 3We’re 6 people at $30k MRR. Should we open-source our sync SDK before the Series A pitch in May, or keep it closed until we’ve raised?
Chief of staff
A real argument needs real sides. The Strategist argues for opening it, The CFO against, and The Engineer weighs what it costs to maintain in public. Each researches alone, then they react once to one another.
The StrategistCompetitive Expert
The CFOFinancial Controller
The EngineerTechnical Builder

Asked first
Who answers issues and pull requests if it goes public?
MeOne of the teamNobody yet
The board’s call
Open-source the SDK in April, under Apache 2.0, and keep the hosted sync service closed.
The CFO changed position after reading The Strategist’s research: three funded rivals already ship open SDKs, so a closed one has become the cost, not the moat. What stays closed is what customers pay for.

The Engineer disagreed
“Nobody owns the issues yet. A public repo with unanswered questions looks worse to investors than a closed one”
Board of 3 · about 95 credits on the card · an example, not a recorded run









