Is fair-trade coordination a feature or a product?

Currently a feature candidate. The signal that promotes it to a standalone product is when a crew explicitly requests it and pays to solve the coordination problem, rather than tolerating it as background friction.

Has any community explicitly asked for contribution-based reputation?

Not yet validated externally. This is the demand gate that determines whether Howzus activates as a standalone venture or reactivates as a Stackmates platform primitive.

Community

Howzus

Q: What would make Howzus worth building that Slack, Discord, and Circle cannot do?

Howzus measures contribution and makes value distribution transparent — something general-purpose chat tools cannot do. The moat is fair-trade economics: when crew members know their contributions are tracked and rewarded proportionally, they stay and build harder.

Fair-trade coordination for crews who build together and share the upside

Think Slow

2/10

Composite

AI-native business plan

The operating-model artifacts this business idea needs.

Howzus is not just a pitch. A venture folder should show the idea, the economics, the go-to-market path, the AI leverage, the delivery loop, and the proof gates needed to run it. Missing artifacts stay visible until they are authored.

Artifacts

Covered

Needed

Cash Flow Model

Needed

Revenue, delivery cost, burn, runway, scenarios, break-even, and kill thresholds.

Cannot fill — no teams interviewed, no pricing tested.

Go-To-Market Plan

Needed

Ideal customer profile, wedge, channels, acquisition loop, 90-day plan, and conversion proof.

Zero customer conversations. Zero pilot communities.

AI-Native Strategy

Covered

Where AI creates leverage, what remains human judgment, and what data compounds.

Voice-first coordination + MCP servers for contribution proof

Offer And Pricing

Needed

Packages, price points, first paid unit, margins, and the smallest sellable promise.

TBD

Lead Magnet

Needed

The diagnostic or proof asset that turns interest into a named prospect.

Missing from the public operating model. This is the next planning gap to author.

Validation Checklist

Covered

Founder readiness, pain evidence, demand signals, risk gates, and next experiment.

Covered on this overview from venture data.

Principles Audit

Needed

Business principles, constraints, leverage, distribution, and what not to optimize.

Missing from the public operating model. This is the next planning gap to author.

Operating Loop

Covered

How the business runs week to week: learn, sell, deliver, measure, improve, teach.

Form a crew of 3. Complete one trade cycle in a week.

Proof And Kill Signals

Covered

Metrics, evidence state, proof gaps, reactivation conditions, and kill criteria.

Kill rationale present; differentiator unproven

Planning standard: cash flow model, go-to-market plan, AI strategy, offer/pricing, lead magnet, validation checklist, principles audit, operating loop, and proof/kill signals. Business instruments hold the reusable templates; venture folders hold the business-specific plan.

Playbook depth

The venture shows the bet. The playbook carries the reusable know-how.

Venture pages should stay specific to the business. When a reader needs depth, context, reusable templates, or the operating model behind the bet, route them into the playbook instead of adding another local nav layer.

Business model

depends-on

How to choose and run the business model after the workflow is redesigned.

Cash flow

proved-by

Model revenue, burn, runway, break-even, scenarios, and kill thresholds.

Go-to-market

applies-to

Define the ideal customer profile, wedge, channels, acquisition loop, and 90-day conversion plan.

Operations

applies-to

How to run the business: process, owners, platforms, gauges, and cadence.

Tech stack

depends-on

Architecture and stack choices, including what Stackmates has built or must build.

Apps

applies-to

What app surfaces and software categories the business model needs.

AI work map

pairs-with

Separate human judgment, agent work, data loops, and automation leverage.

Instruments

depends-on

Use the reusable blueprint library; keep venture folders business-specific.

Tight Five

1Purpose

Why does this matter?

Lots of chat, nothing gets built.

2Principles

What truths guide you?

Contribution proof replaces social performance.

3Platform

What do you control?

Match, commit, deliver, verify, improve.

4Perspective

What do you see others don't?

Completed trades per week is truth.

5Performance

How do you know it's working?

Each trade builds the trust graph.

3/10

Purpose

3/10

Potential

1/10

Capability

1/10

Infrastructure

5P Feedback

Pain3 / 5

MEDIUM

Demand1 / 5

NONE

Edge2 / 5

LOW

Trend3 / 5

MEDIUM

Conversion1 / 5

NONE

Critical Metrics

Critical Path5% / 80%

Nothing built

Critical Mass0% / 60%

Zero communities

Critical Velocity0% / 100%

$0 revenue, $0 burn

Kill Criteria

Pilot teams don't ship

After first 2 pilots

Zero artifacts completed in week one

Can't recruit pilots

Month 2

Fewer than 2 communities in 60 days

Revert to incumbents

After first 2 pilots

Pilot teams go back to Slack/Discord within 2 weeks

Questions

What would make Howzus worth building that Slack, Discord, and Circle cannot do?

Is fair-trade coordination a feature or a product?
Could this reactivate as a Stackmates community primitive rather than standalone?
Has any community explicitly asked for contribution-based reputation?