Membership, not a licenceFour productsOne rule: AI does the work, a person is at the gate

Your subscription funds the team that builds what you ask for.

Four tools for marketing, sales and running a business. Members post problems. Practitioners decide in public. An AI development team builds, a person checks, and the changelog names you. Every week.

How it works  ·  See the queue  ·  Read the changelog

MeYouSocial

[4] days

Request to decision, median

[6] days

Decision to ship, median

[23]

Changes shipped this month

[71]%

Started as a member’s problem

Sample values. Live figures are published monthly. How the scorecard works.


The thesis

Every SaaS company has a feedback board. Almost none of them can afford to act on it.

Software has always been shaped by its users in theory and by its engineering backlog in practice. The gap between the two is where most product frustration lives. Engineering time is the scarce resource, and every request competes with the roadmap.

MeYouSocial inverts that. An AI development team makes the cost of building a change small enough that the scarce resource becomes judgment: deciding what is worth building, for whom, and what the product should refuse to become. That judgment comes from practitioners in marketing, sales and entrepreneurship who use the tools themselves, and from a community of members whose real problems set the agenda.

The result is not a suite of finished products with a suggestion box attached. It is a set of products that are permanently in motion, with a visible loop from a member’s problem to a shipped change, and a community that can watch the loop run.

Why this is possible now

The cost of building collapsed.
An AI development team can take a well-described problem to a verified, tested change in days. Producer is the proof inside the family already: a screen recording to a finished, checked video with a human at three gates and an agent doing the rest.

Practitioners can encode their judgment directly.
The best parts of the products are opinions, not features. LevelUp insists on a weekly review. Publish refuses to publish an unsourced claim. Velocity will not send anything without a human or a dial the human set. Producer will not put a number on screen that is not in the footage.

Ownership moved to the customer.
All four products run on the member’s own AI keys with no metering inside the app. The subscription does not pay for tokens. It pays for the evolution of the product.


The queue · live

What members asked for, and what we did about it.

Product The problem Raised by Status Decided in Shipped
Velocity [Problem statement as the member wrote it] [Member name] Shipped [3] days [date]
Producer [Problem statement as the member wrote it] [Member name] Building [2] days behind a flag
LevelUp [Problem statement as the member wrote it] [Member name] Planned [4] days [sprint]
LevelUp [Problem statement as the member wrote it]Declined by the steward: [the reason in one sentence, citing the charter line it breaks]. [Member name] Declined [6] days –

Every request gets a decision within ten business days. Declines are public, with the reason. Shipped entries name the member who asked. The first entries appear as the founding cohort posts its first problems.

How the queue works


Four products. One rule.

AI does the work. A person is at the gate. All four run on your own AI keys, with no metering inside.

LevelUp

The second brain.
One workspace for everything you’re carrying in your head. Tasks, notes, goals, habits, calendar and money, reviewed on a rhythm, with an assistant that does the work.
Holds that the weekly review is the keystone.
Live at levelupnow.tools
About LevelUp

Velocity

One job: get sales meetings booked.
Find the right people, reach them with outreach written for each one, and book the meeting. Nothing sends without a human or a dial you set.
Holds that every fact carries its source and a confidence score.
Early access
About Velocity

Publish

The content engine that runs mostly on its own.
Research, drafts, review, publishing and distribution to fifteen networks. Claims are sourced, not asserted. Your job is decisions.
Holds that silence means all clear.
Live
About Publish

Producer

Drop a screen recording. Get a finished demo video.
Transcribed, scripted, narrated, built and verified on your machine, with a person at three gates.
Holds that the footage is the source of truth.
Windows, version 0.1.0
About Producer

How a problem becomes a change

Six stages. Each has something you can see and a time we commit to. These commitments are the only promises we make.

1 · Request

Post a problem, not a feature, in the product’s category. The AI team asks clarifying questions in the thread within hours. First response within one business day.

2 · Decision

The steward reads the thread and the usage evidence and marks it Under review, Planned or Declined, with the reason, in public. Decision within ten business days.

3 · Build

The AI team implements the change in a branch behind a flag. You can read the build log: what was read, what was written, what was run.

4 · Verify

Automated regression, layout, accessibility and data-consistency checks, then a small member testing cohort. No release without a passing check.

5 · Ship

Flag on for testers, then for everyone, in the weekly release window. The changelog entry names the member who raised the problem.

6 · Tell

A short changelog video every week and a community call every month walk through what changed and why.
Stage What happens What members see Commitment
Request A member posts a problem in the product’s category. The AI team asks clarifying questions in the thread within hours. The thread, the questions, the answers First response within one business day
Decision The steward reads the thread and the usage evidence and marks it Under review, Planned, or Declined with a reason. The status and the reason, in public Decision within ten business days
Build The AI team implements the change in a branch behind a flag. A build log: what was read, what was written, what was run Started within the published sprint
Verify Automated regression, layout, accessibility and data-consistency checks, then a small member testing cohort. The check results and the testers’ notes No release without a passing check
Ship Flag on for testers, then for everyone. The changelog entry names the member who raised the problem. The changelog, the help article, the flag Weekly release window
Tell A short changelog video and a monthly community call walk through what changed and why. The video, the call, the recording Weekly video, monthly call

Two details matter more than the rest. Declines are published with reasons. A community that only sees acceptances assumes silence means nobody read the request. The changelog names the member. Credit turns a list of fixes into a record of the community’s influence. The full model, with its guardrails.


Four roles, each with clear authority and clear limits

Members

Bring problems, not feature requests. “I lose an hour every Monday reconciling replies across three inboxes” is evidence. “Add a unified inbox” is a guess at a solution. Members also test, use, and tell the community what changed for them. Their weight comes from participation, not volume.

Practitioner stewards

One per product. A working marketer, seller or founder who uses the product daily, holds its point of view, writes its routines, accepts or declines requests in public, and is the person who says no. Without a steward, member-driven development becomes the sum of every request.

The AI development team

Does the work between decision and release. Intake: reading the thread and asking the clarifying questions. Analysis: checking how that part of the product is actually used, with consented data only. Build. Verification: regression, layout and data-consistency checks. Documentation: the help article and the changelog entry. Fast, tireless, non-interactive. It does not decide what to build and it does not release.

The release gate

A human. Nothing reaches all members without a person confirming that verification passed, the change matches the decision, and the help content is ready. The same rule the products themselves follow: AI acts, a person is at the gate.

The suite as evidence

The most persuasive proof that the model works is that the company runs on it.

Producer makes the weekly changelog video from a screen recording of the release.

Publish writes the article, sources the claims, and distributes the video to every network on the publish day.

Velocity runs outreach to prospects and re-engages members who have gone quiet, with every send behind the approval queue.

LevelUp holds the roadmap, the steward’s weekly review, and the decision log.

Each of those is a workflow members can copy for their own businesses. The community learns how to run a company on the products by watching one being run.


How it compares

Each cell in the last column exists somewhere else. All six together, with the numbers to prove it, do not.

Traditional SaaS Open source Agency or custom build No-code platforms Member-evolved
Who decides what gets built Product management Maintainers and contributors The client The user, within the platform’s limits Practitioner stewards, from member problems
Who builds it Engineering team Volunteers and sponsors The agency The user AI development team, human gate
Request to ship Quarters Varies widely Weeks to months, paid Immediate, limited Days, verified
Visibility of the process Roadmap page at best Full, if you read code Private None needed Public loop, build log, scorecard
Who owns the data and keys The vendor The user Depends on contract The platform The member
What the money funds Access and usage Donations or support The build Seats The evolution of the product

Three ways in.

Tiers differ in involvement, never in whose requests get built.

Member

”””[PRICE
” time=”per month”]
  • All four products: LevelUp, Velocity, Publish and Producer
  • The community and the request queue
  • The changelog, every week, with the video
  • The monthly community call, live or recorded
Join as a member

Contributor

”””[PRICE
” time=”per month”]
  • Everything in Member
  • Early access to changes behind flags
  • A seat in the testing cohort
  • Office hours with the stewards
Join as a contributor

Founding

”””[PRICE
” time=”per year, or once · limited to [n]”]
  • Everything in Contributor
  • Lifetime recognition in the changelog and on the site
  • A named advisory slot on one product
  • First call on new products
Become a founding member

The apps run on your own AI keys. There is no metering, no credits and no tokens inside them. Enterprise builds for one organisation are priced as projects and kept separate from the community queue. Prices are placeholders until plans are set.


Built by practitioners. Evolved by the community. Verified before it ships.
We decide in ten days and tell you why.
AI does the work. A person is at the gate.


Monthly community call

[Date] · The stewards walk through what shipped, what was declined, and why. Live for members, recorded for everyone who missed it.

Read about the community