Founding Standard · Version 0.1
Project Transparency
Build boldly. Take enough.
Return the rest to the mission.
A company can build ambitious technology, earn sustainable revenue, and pay people fairly without making unlimited founder wealth its definition of success.
An invitation to other buildersAmbition and restraint can coexist.
Technology can improve lives without treating people as products. A company can earn money without allowing money to become its only purpose. A founder can live well without claiming every dollar created by the work of customers, employees, and communities.
Created by Kevin, Project Transparency is a voluntary operating philosophy built around one commitment: money should serve the mission before it serves the founder.
Profit makes useful work sustainable. It supports employees, protects customer commitments, prepares a company for emergencies, and makes continued invention possible. Success should be measured by the lasting value a business creates and the responsibilities it honors.
Turn a belief into commitments people can see.
State the purpose.
Every participating project names the human problem it exists to solve. Revenue sustains that work; it is not the final purpose of the work.
Pay obligations before the founder.
Customer commitments, employees, contractors, essential operations, taxes, and required reserves take priority. Founder compensation is available only when the project can safely afford it.
Publish a founder ceiling.
Set a clear limit on founder benefit and explain how it is calculated. A ceiling is a maximum, not a guaranteed payment or a debt carried into future years.
Measure real impact.
Define what counts as a person helped, exclude duplicates, and explain the evidence. Registrations and inflated numbers should not stand in for meaningful outcomes.
Keep surplus useful.
After obligations, reserves, and approved founder compensation, remaining resources support the mission through product development, accessibility, security, continuity, research, and community benefit.
Show the difficult parts, too.
Publish missed goals, material problems, corrections, and changes to commitments alongside achievements. Protect customer records, personal information, confidential agreements, and security details.
Show where the money goes.
Each participating project publishes a financial waterfall: the order in which revenue meets responsibilities before founder benefit and further reinvestment.
- Restricted funds and required taxes.
- Customer refunds, service commitments, and contractual obligations.
- Employee wages, benefits, and contractor payments.
- Infrastructure, security, support, and essential operations.
- Insurance, legal compliance, accounting, and risk management.
- Emergency, continuity, and incident-response reserves.
- Approved preservation and community commitments.
- Founder compensation after the fiscal year closes.
- Product reinvestment, accessibility, research, and expanded community programs.
The founding model sets a separate ceiling of $100,000 net founder benefit per project, per fiscal year. Each project defines its impact measure and the potential benefit it creates, subject to that ceiling and the resources actually available after its responsibilities are met.
For Heirloom Digital, the working model is one dollar of potential net founder benefit for each unique Verified Life Supported, up to that annual ceiling. If 100,000 lives are verified but only $40,000 is safely available after the waterfall, founder benefit cannot exceed $40,000.
Associated company costs, including any tax gross-up and employer payroll costs, are reported separately. The ceiling does not increase automatically with inflation. Material changes must be explained publicly.
Make room for the next good idea.
A big part of this model is giving founders a reason to keep creating. A successful idea can pay well. With a separate ceiling for each project, new ideas can create new income while helping more people.
What I want to encourage is a cycle: build something useful, help it become stable, then use some of the time that frees up to work on another problem. A project that reaches its ceiling keeps its surplus working for its mission.
For me, that means I can keep building and earning without needing one idea to generate unlimited personal income. The projects I've already built still need care, support, and a plan for their future. Moving on to a new idea should leave them in good hands.
An explicit boundary
Loom Systems and Project Transparency
Loom Systems is my independent client-services business. It provides paid services to clients and supports my livelihood. Loom Systems itself does not participate in Project Transparency and is outside its founder compensation ceilings and public financial reporting requirements.
Project Transparency is the operating commitment for my mission-driven projects. Loom Systems' website introduces the philosophy and identifies the projects participating in it. Each participating project is responsible for honoring its published commitments.
All of my mission-driven projects participate in Project Transparency. Loom Systems, my independent client-services business, is the sole exception.
Kevin, founder
Transparency is evidence.
A participating project's public reporting should show revenue, major expense categories, reserves, founder benefit actually paid, associated company costs, reinvestment, community allocations, verified impact, and material conflicts of interest.
Figures should say how they were checked: live operational, management reviewed, accountant reviewed, or independently assured. Estimates and targets must be labeled. A polished dashboard does not make a number audited.
The standard calls for a public change log and corrections record, a channel for concerns, a continuity plan, and independent review at a published threshold. When a commitment is broken, the response should include an acknowledgment, an explanation, and a verifiable corrective action plan.
Customers and patrons should be able to suggest priorities and review proposals through clearly defined channels. Participation must respect privacy, individual consent, security, and the project's mission.
Where this stands
This page publishes the founding philosophy and Version 0.1 of the standard. Project-specific dashboards, assurance, and measured results must be published and verified separately. This statement does not claim that those systems or reviews are already complete.
Build something useful. Show another way.
Project Transparency is an invitation to founders, builders, workers, investors, and community leaders. Innovation can reward its creators while preserving dignity, accountability, and shared benefit.
Start with the problem you want to solve. Decide what enough means for founder compensation. Write down your responsibilities and how you will measure impact. Publish the rules, then show the results, including what did not work.
Adapt the model to your mission. Challenge its weaknesses. Improve the measurements. Help demonstrate that extraordinary work does not require unlimited personal extraction.
The objective is to build lasting value and make the commitment visible.
Share an idea or challenge the model: