smartup-zero
/
1_general_forum
1
1
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add wiki templates for 1_general_forum

master
Robbert Schep 2025-08-08 16:53:06 +02:00
parent 5af812f0f1
commit b881df3dbe
10 changed files with 57 additions and 743 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
00_Index.md Normal file

@ -0,0 +1,13 @@
# Smartup Wiki Index
Welcome to the Smartup Wiki.
This space documents objectives, lessons learned, and best practices.
## Sections
1. [Objectives and Phases](01_Objectives_and_Phases.md)
2. [Lessons Learned](02_Lessons_Learned.md)
3. [Best Practices](03_Best_Practices.md)
4. [Challenges and Solutions](04_Challenges_and_Solutions.md)
5. [Metrics and Indicators](05_Metrics_and_Indicators.md)
6. [Archive](99_Archive.md)

12
01_Objectives_and_Phases.md Normal file

@ -0,0 +1,12 @@
# Objectives and Phases
Track current objectives, OSBP references, and Smartup phase notes.
## Current Objectives
-
## OSBP Reference
- Link to OSBP doc:
## Smartup Phase Notes
-

8
02_Lessons_Learned.md Normal file

@ -0,0 +1,8 @@
# Lessons Learned
Document key insights and decisions from team sessions.
## Sessions
<!-- ENGELBOT:LESSONS-LEARNED-START -->
<!-- ENGELBOT:LESSONS-LEARNED-END -->

6
03_Best_Practices.md Normal file

@ -0,0 +1,6 @@
# Best Practices
Validated strategies, checklists, and methods that worked well.
<!-- ENGELBOT:BEST-PRACTICES-START -->
<!-- ENGELBOT:BEST-PRACTICES-END -->

6
04_Challenges_and_Solutions.md Normal file

@ -0,0 +1,6 @@
# Challenges and Solutions
Record challenges faced and how they were addressed.
<!-- ENGELBOT:CHALLENGES-START -->
<!-- ENGELBOT:CHALLENGES-END -->

9
05_Metrics_and_Indicators.md Normal file

@ -0,0 +1,9 @@
# Metrics and Indicators
Track quantitative and qualitative performance indicators.
## KPIs
-
## Observations
-

404
0_timline-content-stlye-guide.md

@ -1,404 +0,0 @@
This guide ensures consistent content across the 0_timeline website. All contributors should reference this when creating or editing content. Our goal is to make complex ideas accessible while maintaining the experimental, transparent spirit of Smartup Zero.
## 🎨 Visual Language
### Icon Dictionary
Always use these icons for consistency across all pages:
| Concept | Icon Code | Usage |
|---------|-----------|--------|
| **Organizational Structure** |
| General Forum | `:material-forum:` | Public discussions, voting, governance |
| Workplace | `:material-briefcase:` | Worker-only spaces and content |
| Teams | `:material-account-group:` | Team-related content |
| Roles | `:material-card-account-details:` | Role definitions and assignments |
| Objectives | `:material-target:` | Project goals and missions |
| Tasks | `:material-checkbox-marked-circle:` | Individual work items |
| **Project Specifics** |
| ONLIFE | `:material-alert-decagram:` | Emergency network references |
| Smartup Model | `:material-atom:` | Core model concepts |
| Experiment | `:material-flask:` | Scientific method references |
| **Actions & States** |
| Vote | `:material-vote:` | Governance decisions |
| Join | `:material-account-plus:` | Recruitment/onboarding |
| Build | `:material-hammer:` | Development work |
| Success | `:material-check-circle:` | Completed/positive items |
| Warning | `:material-alert:` | Important notices |
| Info | `:material-information:` | Explanations |
| **Financial** |
| Treasury | `:material-currency-eur:` | Money/funding matters |
| Credits | `:material-coin:` | Smartup Credits (SC) |
| **Technical** |
| Code | `:material-code-tags:` | Development/repos |
| Infrastructure | `:material-server:` | Technical stack |
| Communication | `:material-chat:` | Matrix/Element |
### Color Philosophy
- **Primary (Amber)** 🟨: Energy, innovation, warmth - use for main CTAs and highlights
- **Accent (Lime)** 🟩: Growth, freshness, progress - use for success states and secondary actions
- **Semantic Colors**: Use mkdocs-material's built-in admonition colors for meaning
## 📐 Content Patterns
### Page Headers
Every page should start with a clear hierarchy:
```markdown
# :material-icon: Page Title
!!! info "What is this?"
One-sentence explanation of what this page covers.
## Purpose (or The Why)
Brief paragraph explaining why this matters in the Smartup Zero context.
```
### Status Indicators
For showing project or phase status:
```markdown
<div class="grid cards" markdown>
- :material-check-circle:{ .lg .middle } **Completed**
---
What has been achieved
[:octicons-arrow-right-24: View details](#)
- :material-progress-clock:{ .lg .middle } **In Progress**
---
What is currently being worked on
[:octicons-arrow-right-24: Track progress](#)
- :material-calendar-clock:{ .lg .middle } **Planned**
---
What's coming next
[:octicons-arrow-right-24: See roadmap](#)
</div>
```
### Team Cards
Standard format for presenting teams:
```markdown
### :material-account-group: Team Name
!!! tip inline end "Quick Links"
:material-git: [Team Repos](https://smartup-zero-forgejo.fly.dev/smartup-zero/team-name)
:material-chat: [Team Room](#3_team-name)
:material-clipboard-list: [Open Tasks](link)
**Captain:** [@username](link)
**Members:** 5 active contributors
**Formed:** January 2025
**Mission:** One clear sentence describing the team's purpose.
**Current Objectives:**
- Objective 1 with deadline
- Objective 2 with deadline
```
### Phase Documentation
For describing project phases:
```markdown
## :material-numeric-1-circle: Phase Name
!!! success inline end "Phase Status"
**Status:** Active/Complete
**Duration:** 30 days
**Started:** Date
**Target:** Date
### Goals for This Phase
- [ ] Goal 1 with measurable outcome
- [x] Goal 2 (completed)
- [ ] Goal 3 with measurable outcome
### Key Deliverables
| Deliverable | Description | Status |
|-------------|-------------|---------|
| Item 1 | What it is | :material-check: Done |
| Item 2 | What it is | :material-progress-wrench: In Progress |
| Item 3 | What it is | :material-calendar: Planned |
```
### Call-to-Action Sections
For encouraging participation:
```markdown
## :material-rocket-launch: Ready to Contribute?
<div class="grid" markdown>
:material-account-plus:{ .lg }
**Join the Project**
Become a Smartup Zero owner
[Join via Open Collective :material-open-in-new:](https://opencollective.com/smartup-zero){ .md-button }
:material-chat:{ .lg }
**Start Discussing**
Connect with the community
[Enter Matrix Space :material-open-in-new:](#){ .md-button }
:material-hammer:{ .lg }
**Start Building**
Pick up your first task
[Browse Open Tasks :material-open-in-new:](#){ .md-button }
</div>
```
## 📝 Writing Guidelines
### Voice & Tone
- **Inclusive**: Always "we" not "I" or "they"
- **Experimental**: Acknowledge we're learning ("we believe", "our hypothesis")
- **Transparent**: Share both successes and challenges
- **Accessible**: Explain technical terms on first use
### Structure Guidelines
1. **Start with Why**: Lead with purpose/problem before solution
2. **Show, Don't Just Tell**: Use examples and diagrams
3. **Progressive Disclosure**: Overview first, details in expandable sections
Example:
```markdown
## The Smartup Credit System
**Why it exists:** We need a fair way to track and reward contributions before cash arrives.
??? info "How it works (Technical Details)"
Detailed explanation here...
```
### Common Phrases
Use these standardized phrases:
- "Smartup Zero" (not "SmartUp" or "smartup")
- "Smartup Credits (SC)" on first mention, then "SC"
- "the experiment" (lowercase when referring to our project)
- "collective ownership/craftsmanship/governance" (our three pillars)
- "ONLIFE" (all caps - it's an acronym)
## 🧩 Component Library
### Definition Boxes
```markdown
!!! info "Smartup"
A new organizational model based on collective ownership, collective
craftsmanship, and collective governance.
```
### Warning Boxes
```markdown
!!! warning "Experimental Phase"
This process is still being tested in our micro-pilot.
Procedures may change based on learnings.
```
### Example Boxes
```markdown
!!! example "How This Works in Practice"
When a developer completes a task worth 500 SC, the Team Captain
approves it, triggering an automatic ledger update...
```
### Quote Boxes
```markdown
!!! quote "Our Inscription"
We don't accept our reality but seek to alter it. We are not too late
or too early but precisely on time...
```
### Tabs for Multiple Perspectives
```markdown
=== ":material-account: For Contributors"
Information relevant to people wanting to contribute...
=== ":material-currency-eur: For Supporters"
Information for financial supporters...
=== ":material-cellphone: For Future Users"
Information about using ONLIFE...
```
### Expandable Details
```markdown
??? question "Frequently Asked Question"
The answer to the question...
??? tip "Pro Tip"
Advanced information for experienced users...
```
### Button Styles
```markdown
[Primary Action :material-arrow-right:](#){ .md-button .md-button--primary }
[Secondary Action](#){ .md-button }
[Text Link with Icon :material-open-in-new:](#)
```
### Mermaid Diagrams
```markdown
```mermaid
graph TD
A[Contributor] -->|Creates| B[Task]
B -->|Completes| C[Review]
C -->|Approves| D[SC Minted]
D -->|Logged in| E[Ledger]
```
```
### Progress Indicators
```markdown
!!! progress "Project Completion"
:material-progress-check: **65% Complete**
- [x] Phase 0: Micro-Pilot
- [x] Infrastructure Setup
- [ ] ONLIFE MVP
- [ ] First Funding Round
```
## 🔧 Technical Formatting
### Code Blocks
Always specify language for syntax highlighting:
```markdown
```python
def mint_credits(worker, amount):
"""Mint Smartup Credits for completed work."""
return ledger.add_entry(worker, amount)
```
```
### File References
```markdown
!!! file "ledger.log"
```json
{"type": "mint", "worker": "@alice", "amount": 500, "task": "#42"}
```
```
### Terminal Commands
```markdown
```console
$ git clone https://smartup-zero-forgejo.fly.dev/smartup-zero/0_timeline.git
$ cd 0_timeline
$ mkdocs serve
```
```
## 📊 Tables and Data
### Standard Table Format
```markdown
| Column | Column | Column |
|--------|--------|--------|
| Data | Data | Data |
| Left-aligned | Center-aligned | Right-aligned |
```
### Status Tables
```markdown
| Component | Status | Notes |
|-----------|--------|-------|
| Matrix Server | :material-check-circle: Operational | 99.9% uptime |
| Forgejo | :material-check-circle: Operational | v1.21.3 |
| Engelbot | :material-progress-wrench: In Progress | v0.1 pending deploy |
```
## 🌐 Linking Strategy
### Internal Links
- Use relative paths: `[Team Structure](../smartup-zero/3_teams.md)`
- Link to sections: `[Voting Process](1_general_forum.md#voting)`
### External Links
- Always add icon: `[Open Collective :material-open-in-new:](https://opencollective.com/smartup-zero)`
- Use descriptive text, not "click here"
### Cross-References
```markdown
!!! seealso "Related Topics"
- [The Smartup Model](../0_timeline/the-smartup-hypothesis.md)
- [How to Contribute](../smartup-zero/2_workplace.md)
```
## ✅ Checklist for New Pages
Before publishing any new page, ensure:
- [ ] Uses appropriate icon in title
- [ ] Has "What is this?" info box
- [ ] Follows voice & tone guidelines
- [ ] Includes at least one visual element (diagram, table, or card grid)
- [ ] Has clear CTAs if applicable
- [ ] Links to related content
- [ ] Uses consistent terminology
- [ ] Mobile-friendly (test grid layouts)
## 🚀 Quick Start Template
Copy this template when creating new pages:
```markdown
# :material-icon: Page Title
!!! info "What is this

3
99_Archive.md Normal file

@ -0,0 +1,3 @@
# Archive
Outdated information and closed learnings are stored here for reference.

195
From-0.md

@ -1,195 +0,0 @@
july 4 2025
##: What We’re Setting Up – `0_timeline`
The `0_timeline` is the **public-facing layer of the Smartup** — a static website auto-generated from the internal Forgejo repo structure. It brings **transparency** and **momentum** to the project.
---
what is it??
This project is a simple static site built with MkDocs and Material theme, deployed on Clever Cloud using a lightweight Python HTTP server. The setup is minimal and straightforward, relying on Python virtual environments and Clever Cloud’s deployment hooks.
### 🔍 Purpose
#### 1. **Transparency**
Let the outside world monitor:
* What we’re building
* Why we’re building it
* Who’s involved
#### 2. **Recruitment**
Help new contributors:
* See open roles and get involved
* Understand governance, credits, and roadmap
* Follow live progress (issue milestones, bounties, completed tasks)
### 🧱 Architecture Goals
| Feature | Description |
| ------------------------ | ---------------------------------------------------------------------- |
| **Auto-generated** | Site built directly from Forgejo repo structure — no duplicate content |
| **Readable** | Clear, accessible UX for outsiders and first-time visitors |
| **Live & Synced** | Always reflects current status of governance, code, funding |
| **Static & Lightweight** | No backend, served from Clever Cloud or similar (HTML + JS bundle) |
---
### 📦 Content Sources
The site will pull structured content from:
* `README.md` / `SUMMARY.md` from `docs/`
* Issues and Milestones in `forgejo` repos
* Ledger and Credit updates from `smartup-credit`
* Roles and contributor list from `governance/` repo
* Public-facing objectives (like this brief) from `0_timeline.org` itself
---
### 🛠 Tech Stack (Proposed)
| Component | Tool |
| --------------------- | ------------------------------------------- |
| Static Site Generator | `mkdocs` |
| Theme | `mkdocs-material` |
| Nav generation | `awesome-pages` plugin |
| Git-based metadata | `git-revision-date-localized-plugin` |
| Remote content | `mkdocs-monorepo-plugin` or symlinks |
| Deployment | Docker → Clever Cloud |
| Search | Built-in (lunr.js), works offline |
| Styling | Comes with great defaults (Material UI) |
*
---
### ⏱ What We Did Today
1. **Set up project folder** `1_general_forum` with `docs/` and `mkdocs.yml`.
2. Created a Python virtual environment (`venv`) and activated it.
3. Installed MkDocs Material theme and plugins.
4. Created `docs/index.md` with sample content.
5. Configured `mkdocs.yml` for site name, theme, nav, and plugins.
6. Tested the site locally with `mkdocs serve` — site displayed correctly.
7. Generated `requirements.txt` with `pip freeze`.
8. Created Clever Cloud config file `.clevercloud/python.json` specifying:
- Python 3.11 runtime
- Build command: `pip install -r requirements.txt`
- Start command: `mkdocs build && python -m http.server --directory site $PORT`
9. Initialized git repo and pushed to Clever Cloud for deployment.
## Debugging and Current Status
- Deployment on Clever Cloud **fails to start properly**.
- Verified Python 3.13 is used, config file is present.
- Checked build logs: no obvious package errors, but the server does not serve site as expected.
- Confirmed that `mkdocs build` generates `site/` folder locally.
- Start command uses `python -m http.server --directory site $PORT` — unsure if Clever Cloud correctly passes `$PORT` or if `http.server` works as intended.
- Domain `timeline0.org` DNS settings not verified yet due to deployment issues.
## Where We Are Stuck
- The app does not deploy and serve correctly on Clever Cloud.
- Need to confirm:
- Correct Python version compatibility.
- Correct start command syntax (especially `$PORT` usage).
- That the built static files exist and are accessible on the server.
- Need further debugging with Clever Cloud logs and possibly adjusting deployment config.
after some more debugging:
After some debugging:
It turns out that you’re fighting the Python buildpack’s “uWSGI or bust” logic: by default any Python app on Clever-Cloud must supply a CC_PYTHON_MODULE (so it can spin up uWSGI). If you remove that var, the buildpack refuses to start anything. If you set it to “none,” it tries to import a module called none under uWSGI and blows up.
You have two clean ways out:
— Option A: Switch to a static site app on Clever-Cloud
— Option B: Ship your own container (Docker) and completely bypass the Python buildpack
I’ll outline both. Pick the one you prefer:
––––––––––––––––––––––––––––––––
Option A: Use Clever-Cloud’s Static Site “Flavor”
––––––––––––––––––––––––––––––––
In the Clever-Cloud Console, click + New app → Static Sites
Link it to your Git repo (same repo you’ve been pushing)
In the “Build command” field enter:
pip install -r requirements.txt && mkdocs build
In the “Output Directory” field enter:
site
Save & deploy.
• Clever-Cloud’s Static Sites service will run your build, then serve the site/ folder as plain static files off HTTP(S).
• No uWSGI, no CC_PYTHON_MODULE, no hacking start scripts.
• Logs will show the pip install, the mkdocs build, and then “serving static directory.”
When it goes green, point your DNS (CNAME or A record) at the static-sites endpoint and you’re done.
Given that 0_timeline is purely a static website whose content is auto-generated from your Forgejo repos, the path of least resistance—and the most “Cloud-native” way on Clever Cloud—is to treat it as a Static Site rather than a “Python Web” application.
Here’s why and how:
You have zero dynamic backend code.
MkDocs produces a self-contained site/ folder of HTML/CSS/JS.
Clever Cloud’s Static Site service will:
• Run your build command,
• Publish the site/ directory to a CDN-backed endpoint,
• Handle SSL/DNS for you,
• Give you automatic cache invalidation on each deploy.
STEP BY STEP: “STATIC SITE” ON CLEVER CLOUD
In the Clever Cloud console, create a new application of type Static Sites
– Give it a name (0-timeline or similar).
– Link it to your Git repository (the same repo you’ve been pushing).
Configure the build:
Build Command:
bash
Copy Code
pip install -r requirements.txt && mkdocs build
Output Directory:
Code
Copy Code
site
Commit any missing pieces to your repo:
requirements.txt listing mkdocs + material + plugins
mkdocs.yml + docs/ as you already have
(No start.sh or python.json needed here)
Push your changes:
bash
Copy Code
git add requirements.txt
git commit -m "Prepare for Clever Cloud Static Site: add requirements.txt"
git push origin main
Clever Cloud will pick it up, run pip install… && mkdocs build, then serve the site/ folder.
Watch the deployment logs in the Static Site dashboard. You should see:
Code
Copy Code
> pip install -r requirements.txt
> mkdocs build
Building documentation...
Finished in x.xs
Publishing site/
When it’s “Published,” the dashboard will show your https://something.static.cleverapps.io/ URL.
– Test it: you should see your MkDocs site live.
– Under “Domains,” you can attach your custom domain (timeline0.org) with a CNAME record.
BENEFITS
• No fiddling with uWSGI or Python buildpacks.
• Zero extra runtime processes—just a fast static host & CDN.
• Automatic SSL, cache invalidation, rollbacks.
• Works out-of-the-box with mkdocs-material’s JS/CSS bundles, search, etc.
---
It is now deployed and running on clever cloud.

144
Smartup-Business-principles.md

@ -1,144 +0,0 @@
## Smartup Business: Building a 24/7 SDG Enterprise
We're not building a charity. We're not seeking donations. We're creating a new kind of business—one that measures success in SDG progress rather than profit margins, pays competitive rates for real work, and operates 24/7 across the globe. This chapter documents our economic model: how money flows in, how work gets valued, and how ownership creates both efficiency and equity.
### The Business Reality
When we look at traditional approaches to SDG challenges, we see a pattern: NGOs burn out on donation fatigue, social enterprises get pulled toward profit over purpose, and volunteer projects can't sustain professional quality. We need something different—a model that combines business discipline with public good DNA.
A Smartup is that hybrid. We attract top talent because we pay fairly. We maintain quality because we have professional standards. We stay mission-aligned because our owners are our workers, and our success metrics are SDG-based, not profit-based. But make no mistake—this is a business operation designed to be financially sustainable and professionally competitive.
### Revenue Model: The Four License System
Every Smartup needs capital to operate. Traditional startups sell equity to VCs. We sell membership to our community. But unlike traditional equity, every license—whether bought for €200 or €5000—carries exactly one vote and one equal share of future success.
**Individual Licenses:**
The Campaign License (FREE) ensures we never exclude based on wealth. Campaign members help spread awareness, access public information, and can upgrade to paid tiers when able. This is our gateway—especially important for students, people from low-wage countries, and those wanting to explore before committing.
The Watch License (starting at €100 in validation phase) grants full ownership rights and General Forum access. Watch owners participate in all governance decisions, see all documentation, and hold equal shares in future success. They just can't claim tasks or access operational spaces—perfect for supporters who believe in the mission but can't contribute time.
The Work License (starting at €200 in validation phase) includes everything in Watch plus full operational access. Work owners can claim tasks, earn SC, join teams, and actively build the product. This is for those ready to roll up their sleeves and create value.
**The Organizational License (starting at €5000):**
Here's where we bridge individual contribution and institutional support. Universities, ethical businesses, NGOs, and research institutions can become Smartup owners. They get one vote (maintaining democratic balance), can designate one representative, and gain something valuable: a professional training ground for their people.
Imagine a university using Smartup Zero to give computer science students real-world experience building emergency communication systems. Or an ethical tech company having employees contribute to ONLIFE development as part of their learning budget. The organization supports SDG progress while developing their people's skills.
This license type also simplifies grant administration. Instead of complex partnership agreements, supporting organizations can simply purchase a license and have a clear, transparent relationship with the Smartup.
**Price Progression:**
Each Smartup's Leadership Team sets prices based on their needs, but prices always increase through phases. Early supporters take more risk and get lower prices. Later joiners pay more but get more certainty. We announce price increases transparently, creating urgency while respecting that each phase delivers more value.
### Labor Economics: How Work Gets Valued
The heart of our business model is simple: we pay people fairly for good work. But in the early phases, we don't have cash—so we created Smartup Credits (SC).
**The SC System:**
One SC equals one EUR claim on our treasury. The only way to earn SC is by completing tasks. No SC for meetings, no SC for "being around," no SC for having good ideas. You want SC? Pick up a task, complete it well, get it approved.
Every task has a pre-assigned bounty. A senior developer might see "Implement mesh networking protocol - 2000 SC" and know exactly what they'll earn before starting. This prevents favoritism and negotiation fatigue. The work is worth what it's worth.
The 90/10 split drives our learning culture. The attacker (main worker) gets 90% of the bounty. The defender (assistant/learner) gets 10%. This isn't charity—the defender provides real value through quality assurance and documentation. But it also means senior contributors are incentivized to mentor juniors. Every task becomes a teaching opportunity.
**Treasury Management:**
We cap outstanding SC at 3x our cash treasury. This prevents runaway inflation and ensures SC maintains value. When crowdfunding succeeds or grants arrive, we open redemption windows following FIFO (first in, first out) rules. Those who contributed earliest get first opportunity to cash out.
But here's where it gets interesting: many choose to hold their SC. Why? Because as the Smartup grows and attracts more funding, the treasury grows. Your 1000 SC claimed when treasury was small becomes fully redeemable when treasury is large. We're betting on our collective success.
The entire ledger lives in public view. Every SC minted, every redemption, every team budget—transparent to all owners. No hidden executive bonuses, no secret deals. Just clear value exchange for real work.
### Social Capital: The SK System
Money isn't the only currency that matters. Smartup Karma (SK) recognizes contributions that SC can't measure: the teammate who always helps others debug, the member who mediates conflicts, the captain who builds team morale.
SK can't be bought, sold, or transferred. It's earned through peer recognition and quality contributions:
- Excellent defender feedback that helps others learn
- Leading difficult missions successfully
- Creating documentation that saves others time
- Moderating forums fairly and consistently
- Proposing ideas that advance our mission
SK decays 10% monthly, preventing "founder privilege" where early members dominate forever. Stay active and valuable, maintain your SK. Coast on past contributions, watch it fade.
What does SK buy you? Not power, but opportunity:
- 50 SK: Propose in General Forum
- 100 SK: Apply for Team Captain
- 200 SK: Lead missions
- 500 SK: Join Leadership Team, get 1.5x vote weight (capped)
This creates natural leadership paths. Those who consistently contribute quality
work naturally gain influence. But influence has limits—maximum 1.5x vote weight ensures no one dominates regardless of karma.
The dual currency creates healthy dynamics. High SC but low SK? You're a great individual contributor but need to engage more with community. High SK but low SC? You're a community pillar—maybe consider taking on more tasks. Both high? Natural leaders emerge organically.
Business Operations
Financial Flows:
Money enters through three clean channels: crowdfunding rounds, organizational licenses, and research grants. No venture capital, no corporate investment, no strings attached. This isn't ideological purity—it's practical. The moment we take traditional investment, our incentives distort toward exit strategies rather than SDG impact.
Each phase requires new crowdfunding. Validation might need €50k to prove the concept. Design might need €200k for architecture and planning. Production could require €500k for actual building. Organization might seek €1M for market launch. These aren't fixed—each Smartup's Leadership Team proposes budgets based on real needs, and the General Forum approves.
Team captains receive monthly budgets and fight for their allocations in open Leadership Team meetings. Everything is visible: how much each team requested, what they're building, how they're spending. This creates natural efficiency—waste is immediately visible to all owners.
Competitive Advantages:
We compete with traditional tech companies for talent. Here's why we win:
Global talent pool operating 24/7: A developer in Berlin hands off to a designer in Bangkok who passes to a tester in São Paulo. The work never stops.
Zero office overhead: No Silicon Valley rents, no corporate campuses. Every euro goes to actual work.
Intrinsic motivation: People choose us because they believe in the mission. That passion translates to quality.
Learning-while-earning: Our buddy system means every senior task trains a junior. We're building tomorrow's experts while delivering today's work.
Radical transparency: No office politics, no hidden agendas. Energy goes to building, not navigating corporate dynamics.
From Smartup to Market: The Ownership Revolution
Here's where our model becomes revolutionary. After four phases of collective building, when the Smartup launches its market entity, something beautiful happens: the Book of Owners becomes a shareholder registry.
If 1000 people own licenses when we launch, each owns exactly 1/1000 of the business. Doesn't matter if you founded it or joined in phase 4. Doesn't matter if you bought a €200 work license or a €5000 organizational license. One owner, one share.
This creates natural efficiency. Want bigger shares? Keep the team focused. Need more help? Accept dilution. The tension between growth and ownership percentage drives right-sized teams. No bloat, no empire building, just enough people to succeed.
But the relationship doesn't end at market launch. The Smartup community becomes the business entity's strategic asset:
For ONLIFE (the business):
Hire from people who built the product
Beta test with users who understand the vision
Consult experts who retain institutional knowledge
Access a loyal community of shareholder-advocates
For Smartup Zero (the community):
First access to job opportunities at ONLIFE
Paid testing and consulting contracts
Shareholder returns from business success
Continued involvement with the project they built
Some owners might become employees (double benefit). Others remain external shareholders who occasionally contribute through testing or consulting. The community stays vibrant because there's ongoing value exchange, not just nostalgia.
The Numbers Game
Let's be concrete. Say Smartup Zero succeeds:
500 people contribute during Smartup phases
ONLIFE launches serving 100,000 users
Generates €2M annual profit within 3 years
Each owner receives €4,000 yearly dividend
Not life-changing money, but meaningful. Now multiply: what if owners participate in multiple Smartups? What if ONLIFE grows to millions of users? What if the model spawns thousands of Smartups tackling different SDGs?
We're not promising riches. We're demonstrating that doing good and doing well aren't mutually exclusive. Professional quality, fair pay, shared ownership, SDG impact—all in one model.
Why This Works
Traditional businesses optimize for shareholder value, often at society's expense. Traditional NGOs optimize for social good but struggle with sustainability. We're proving a third way: businesses that measure success in SDG progress while maintaining professional operations and fair economics.
The Smartup model aligns everyone's interests. Workers are owners. Owners are community members. Community members are stakeholders in success. When ONLIFE helps a community coordinate during crisis, we all win—financially and morally.
This isn't charity. It's not volunteerism. It's professional business designed for the challenges of our time. We work 24/7 because the SDGs can't wait. We pay fairly because talent deserves reward. We share ownership because collective problems require collective solutions.
Welcome to the business of building a better world. Professional, sustainable, and uncompromisingly focused on what matters.