ChartersReviewed quarterly
What each product is for, what it holds, and what it will never become.
A charter is the one page that keeps a member-evolved product from becoming the sum of every request. Each steward maintains theirs. Every accepted request cites the charter line it serves. Every decline cites the line it breaks. Charters are reviewed with the community once a quarter, and a change to a charter is announced like a release. Steward names are placeholders until assigned.
What a charter contains
1 · What it is for
2 · Who it is for
3 · The opinions it holds
4 · What it will never become
5 · What members can ask for
6 · How it fits the family
7 · The routine
LevelUp
The second brain. One workspace for everything you are carrying in your head.
Steward: [name] · Home: levelupnow.tools · Status: live
What it is for
Running one person’s work, life and money in one connected place, reviewed on a rhythm, with an assistant that does the work rather than describing it.
Who it is for
For: the solo operator, founder, executive or project lead who juggles tasks, notes, goals, habits, a calendar, a budget and a small pipeline, and wants one cockpit over all of it. Small teams who share assignments and keep their own workspaces private.
Not for: organisations that need enterprise resource planning, portfolio governance or time-and-billing. Teams that want a shared sales CRM. Anyone who wants an app to move their money for them.
The opinions it holds
- Capture is cheap, sorting is deliberate. Getting a thought in takes a keystroke. Deciding what it means happens in a review.
- Links are the point. A task, a note, a goal, a project and a contact reference each other in both directions. That is what makes the assistant useful.
- The weekly review is the keystone. Everything else degrades without it. The product builds the daily, weekly and monthly rhythm in and will not remove it.
- The assistant acts, but asks first. Every change is an approval card. Deletes always ask. Everything has an undo. When two things match, it shows the candidates instead of guessing.
- Money is private by default. Not visible to admins, not visible to anyone it was not explicitly shared with.
- Nobody uses all of it, and that is fine. The detail dial hides pages. It never deletes them.
What it will never become
- An enterprise work-management platform. It mirrors Smartsheet and Nifty and syncs status back. It is one person’s view over the tools their teams already use, not a replacement for them.
- A bank or a trading platform. Money reads accounts through a read-only bridge. It never initiates a payment or a trade.
- A shared sales CRM. Contacts and Pipeline are personal scale. Velocity is the CRM.
- A messaging product. Mail is a connected inbox with triage, not a chat platform.
- A content publisher. Ideas start here and go to Publish.
What members can ask for
In scope: a Home widget, a report template, a sheet or slide template, a review routine improvement, a sync with a task or calendar tool you already use, a Money report or agent.
Out of scope: team chat, payment initiation, a website builder, workspace-wide visibility for admins.
How it fits the family
The personal cockpit. Pipeline work at team scale goes to Velocity. Articles and posts go to Publish. Demo videos go to Producer. Daily and weekly digests arrive here. These are workflow handoffs, not built integrations, until the changelog says otherwise.
The routine
Five minutes in the morning on the Planner. Five minutes at shutdown. Thirty minutes on the weekly review. A monthly pass over Reports, Money and goals. A quarterly reset.
Velocity
The unified revenue platform. One job: get sales meetings booked.
Steward: [name] · Home: getvelocityai.app · Status: early access until the August test report’s top remediation items ship
What it is for
Finding the right people, reaching them with outreach written for each one, booking the meeting, closing the deal and keeping the customer, with a human or a dial the human set in front of every send.
Who it is for
For: sales teams, founders doing their own outbound, and agencies running outbound for several clients from one login. Reps who work a queue. Managers who set the dials and read the numbers.
Not for: customer support teams that need ticketing. Consumer brands sending bulk newsletters. Anyone who wants outreach with no approval step and no sending limits.
The opinions it holds
- Meetings are the job. Every feature exists to feed booked meetings. A feature that does not is suspect.
- Nothing sends without a human or a dial. Every autonomous feature has the same three-way control, Off, Approve, Auto, and the dials are admin-only.
- Approve is a dry run on real data. The AI does the work and stops. Promote a dial to Auto only when you find yourself approving everything unchanged.
- The data explains itself. Every fact on a person or company carries its source and a confidence score. Verified beats inferred. A human pin beats every provider.
- Home tells you what needs you. One attention panel for every queue waiting on a person. An empty panel means the machines are handling it.
- The assistant proposes, a person confirms. It never composes and sends arbitrary email, never deletes, and never touches team, credentials, billing or settings.
What it will never become
- A helpdesk. Customer Success tracks health, renewals and QBRs. It does not run a ticket queue.
- A content or social publishing platform. Landing pages, forms and chat agents capture leads. Writing and distributing content is Publish’s job.
- A bulk-mail cannon. Daily caps, warmup, suppressions and unsubscribe handling apply to every sender. No mode removes them.
- A data broker. Contact data enriched in a workspace stays in that workspace and is never pooled or resold.
- A personal task manager. Tasks here are sales work. Life runs in LevelUp.
What members can ask for
In scope: a new reply class, a new autopilot that starts in Approve, a report or dashboard, a sending or enrichment provider, a workflow-rule trigger or action, a fit-scoring signal.
Out of scope: a ticketing queue, removing an approval gate from any send path, a mode that bypasses suppressions or LinkedIn limits, an assistant that sends without a confirm card.
How it fits the family
The revenue engine. Content that generates inbound comes from Publish. Demo videos for sequences come from Producer. A rep’s personal planning lives in LevelUp. Workflow handoffs, not built integrations, until the changelog says otherwise.
The routine
Ten minutes a day on the Home attention panel. Forty-five minutes a week on Engine Performance, campaigns, conversations, data health and forecast. Monthly: budgets, scoring, the ICP, and promoting one dial from Approve to Auto.
Publish
The content engine that runs mostly on its own. Your job is decisions, not production.
Steward: [name] · Status: live, part of the MeYouSocial family
What it is for
Researching what is worth saying, drafting articles and social posts with their images and SEO, reviewing its own work against hard gates, publishing on a schedule, distributing to every network, and pulling the results back in.
Who it is for
For: companies without a content team, where one person runs a weekly article and a daily social presence in five minutes a day. Agencies and multi-brand operators with a sealed workspace per client. Creators with a YouTube channel who want scripts, thumbnails and production in the same loop. Teams that need roles, approvals and an audit log.
Not for: organisations that want a digital asset manager. Brands that want paid-ad management. Anyone who wants an AI that writes whatever it is told without sourcing.
The opinions it holds
- Gates review as well as block. Nothing AI-made reaches an audience until metadata, slug, keyword, alt text, sourced claims and a branded preview image all pass.
- Claims are sourced, not asserted. Live search finds a source, an independent judge confirms it supports the sentence, and an unsupported claim waits for a person with two buttons: verify or drop.
- Every AI image is looked at. A vision model checks each render. After two failures it stops spending and asks.
- Never an invented number. A dash means not measured, never zero.
- Silence means all clear. A quiet morning sends no digest, on purpose, so the emails that arrive mean something.
- Approving is a person’s act. Only approved ideas are drafted. Publishing an article and approving a social post are always an admin’s act. Full autonomy presses the buttons a person would. It does not lower what they check.
- Bring your own keys, keep your own data. No billing, credits or metering inside the app. Co-branded for agencies, never white-labelled.
What it will never become
- A generic AI writer. Everything it writes is grounded in brand context, motifs, expert profiles and sourced claims. There is no blank chat box that produces ungrounded copy.
- A paid-ads platform. Organic articles, social and video only.
- A brand-monitoring or sentiment tool. Intel measures competitor video outliers to find ideas. It does not watch the internet for mentions.
- A white-label product. The client’s identity leads. The product stays visible.
- A metered marketplace. No credits, no tokens, no in-app billing.
What members can ask for
In scope: a new network, a new gate or check, a new motif, a report block, a CMS export format, an Optimize finding type, a research source, a video-studio step.
Out of scope: an ads module, white-labelling, in-app credits, a publish path that skips the gates, AI-generated brand differentiators.
How it fits the family
The content and distribution layer. It distributes what Producer makes. The leads its content generates are Velocity’s to work. Editorial ideas can start in LevelUp. Workflow handoffs, not built integrations, until the changelog says otherwise.
The routine
Five minutes a day on the Inbox. Half an hour the day before publish day: triage ideas, read drafts, answer knowledge cards, approve and queue the social week. An hour a month on Insights, Motifs, dials and a content audit.
Producer
Drop a screen recording. Get a finished demo video.
Steward: [name] · Status: version 0.1.0, Windows · The brief lists it as VidProducer; one name to be chosen
What it is for
Turning a raw screen recording into a narrated, branded, verified demo video, with a person at three gates and an agent doing everything between them.
Who it is for
For: product marketers, sales engineers, founders, customer success and internal communications teams who have a recording and a message. Agencies producing demo videos for clients in a consistent house look.
Not for: talking-head or live-action editing. Multi-camera or colour-graded productions. Anyone without a Windows PC and a Claude subscription, for now.
The opinions it holds
- The footage is the source of truth. Every number, label and claim in the narration must be visible in the recording. Nothing is invented.
- Narration drives timing. The real length of each recorded line sets the length of its scene. Callouts land on the spoken word, never at the top of the scene.
- A build is not done until the check passes. Lint, check, the seam gate and midpoint snapshots, every time. If it fails, the agent fixes it and runs it again.
- Three gates belong to the person. The brief, the locked script, and the Studio. Everything between them is automatic.
- The agent never renders and never touches narration. Rendering and voice recording are the app’s, and happen when a person presses the button.
- Templates are copied, not reinvented. Every scene starts from an approved reference scene so every video in a workspace looks like one house.
What it will never become
- A general video editor. No timeline for live-action, multi-cam or grading. The input is a screen recording and the output is a demo.
- An avatar or stock-footage generator. Every frame comes from your recording or the template. No synthetic presenters, no generated b-roll.
- A video host or analytics platform. The deliverable is a file. Publish distributes it and measures it.
- A cloud service that holds your recording. Transcription, narration and rendering run on your machine. Claude sees the transcript and selected frames, nothing more.
What members can ask for
In scope: a template look, a narration voice, a package output such as a vertical cut, an input format, a verification check, a brief field, a Studio control.
Out of scope: a live-action editing timeline, AI presenters, generated footage, an agent that renders or re-voices on its own.
How it fits the family
The video maker. Publish distributes what it produces. Velocity uses the videos in sequences and on landing pages. Production tasks are tracked in LevelUp. Workflow handoffs, not built integrations, until the changelog says otherwise.
The routine
Per video, not per week. Write a one-sentence message before anything else. Read the script before you record it. Look at the snapshots before you render. Two to three minutes of video, about ten minutes of your attention.
A request that fits the charter gets built quickly.
A request that breaks it gets a public, reasoned decline. Either way you hear within ten business days.
