Internal · operating system
Intake, proposals, 14-day delivery, claims, creators, partner intros and the house playbook. Live on this device. Seeded, then anything you submit.
Applications
5
Qualified
60%
Proposals
2
Won
1
Sprint tasks
6/14
Brief list
1
49 cards · operator action required on every card
01 · Direction
RCA Pad sells B2B commercial launch services. It must not accept investor funds, custody assets, sell or allocate tokens, execute trades, operate a venue, give investment advice, promise fundraising outcomes or describe offerings as approved without a verified legal basis.
02 · Direction
Canonical brand is RCA Pad on RCApad.com. RCAICO is an acquisition programme for ICO-intent issuers. RegCA.xyz is community and category content. Do not launch duplicate companies or duplicate the commercial site.
03 · Direction
The job is not a 2017 retail ICO funnel. It is helping credible token, protocol, tokenisation, stablecoin and Web3 teams operationalise a launch: evidenced claims, specialist providers, a controlled campaign workflow and durable community demand.
04 · Direction
Thirty-day: five paid Sprints, two converting to Build, ten founding partners. Twelve-month: premium implementation, retainers, a paid partner network, an issuer dataset and an initial workflow product.
05 · Direction
RCA Pad is the master brand. RCAICO Launch is the ICO-intent programme. RegCA.xyz carries community stories. All domains route to purpose-specific pages on RCApad.com until each has a genuine standalone job.
06 · Direction
Commercial launch infrastructure for crypto-asset offerings. Not an exchange, fundraising intermediary, regulated adviser, token seller, official Reg CA platform or investment marketplace.
07 · Direction
Named founders, incorporated or incorporating, a product/testnet/pilot, a launch milestone in 30–180 days, a meaningful budget, substantiated claims and a credible security and legal plan.
08 · Direction
Score team, product, timing, budget, token transparency, security, legal posture, marketing conduct, geography and decision-maker access. Hard-reject anonymous teams, performance promises, token-only pay and retail allocation ops.
09 · Direction
Lead with a 14-day Launch Sprint. Upsell Launch Build for production assets. Retain the strongest clients for campaign operations, creator management, content, partner coordination and post-launch communications.
10 · Direction
Fixed fees, milestone payments, prepaid retainers. Sprint £3,500–£7,500. Build £10,000–£35,000. Managed growth £5,000–£25,000+/mo. No percentage of raise. No token compensation until counsel confirms a lawful structure.
11 · Demand
Application first. Screen before calendar. Thirty-minute qualification. Proposal within 24 hours. Deposit, then structured onboarding. Calendar access is never automatic.
12 · Demand
Home, Sprint, ICO Launch, Partners, Reg CA, Insights and Policies. One primary conversion action and a credible disclosure on every page.
13 · Demand
Lists built from real triggers: funding, testnet, mainnet, ecosystem announcements, tokenisation roadmaps, partnerships and launch dates. Outreach names the product and the immediate milestone.
14 · Demand
Recruit law, security, KYC/AML, tax, tokenomics, formation, custody, infrastructure and specialist communications. Offer visibility, co-marketing, a referral process and market intelligence. Do not promise lead volume you do not have.
15 · Demand
Publish what founders save: launch checklists, claims controls, creator approval, token narrative, data-room planning, partner-stack maps and commentary on the proposed Reg CA framework.
16 · Demand
Weekly Launch Brief, founder interviews, partner sessions, X threads, curated launch stories and a waitlist. Community content must not become an uncontrolled retail investment-promotion feed.
17 · Demand
Vetted roster with disclosure, pre-approval, prohibited claims, geographic restrictions, payment terms, publication evidence and takedown clauses. Archive every campaign post.
18 · Demand
Every client has a claims register: claim, evidence, permitted wording, prohibited wording, approver, audience, channel, date, archive URL and change history. Empty field = not publishable.
19 · Delivery
On payment, open a controlled workspace. Collect entity, team, product, token, security, legal, audience, brand, budget and approvers. Kick-off locks objectives, geographies, owners, SLA and exclusions.
20 · Delivery
Fourteen days: narrative, audience, market map, 90-day plan, funnel, content system, community plan, creator plan, partner map and claims controls.
21 · Delivery
Production: landing pages, messaging, litepaper/FAQ, media kit, social system, CRM/waitlist, community operations, creator briefs, partner outreach and a launch calendar with an approval trail.
22 · Delivery
Keep clients on measurable work: content calendar, community operations, creator management, partner coordination, campaign reporting, update communications and event execution.
23 · Delivery
Structured profiles: category, jurisdictions, buyer fit, minimum, verification, referral SLA and case evidence. “Profile verified” only. Never regulator-like “approved”.
24 · Delivery
Internal record: entity, category, stage, launch date, product evidence, token status, audience, provider gaps, campaign readiness, partner assignments and delivery outcomes. Basis of future intelligence products.
25 · Delivery
Do not custom-build early. Productise only repeated jobs: intake, asset collection, campaign calendar, approval trail, partner tasks, creator brief approvals and reporting.
26 · Controls
MSA, statement of work, client marketing warranty, creator agreement, partner terms, privacy terms, sponsorship policy and rapid takedown. UK and US specialist counsel review the model before scaling.
27 · Controls
Content that invites or induces UK consumer investment activity is high-risk. No public retail purchase journeys, incentives, return claims or token allocations without a documented lawful promotion route.
28 · Controls
Do not describe an offering as SEC-approved or Reg CA-compliant. The proposal is not final. Issuers retain their own securities counsel. Avoid transaction-based compensation pending specialist analysis.
29 · Controls
2FA, role-based access, separate client workspaces, documented permissions, incident contact, deletion schedule. Never store wallet keys, investor identity data or client funds.
30 · Controls
Founder-led sales and strategy first. Then project/account lead, creative/content, community operations, vetted freelance design/development, legal advisers and a partner manager — in that order.
31 · Controls
High gross margin on Sprints, controlled contribution on Builds, durable margin on retainers and partner membership. Track source, conversion, delivery hours, LTV, partner-sourced revenue and churn.
32 · Controls
Applications, qualification rate, calls, proposal rate, win rate, ACV, deposit collection, Sprint-to-Build, Build-to-retainer, partner referrals, delivery margin, Brief subscribers and campaign-control incidents.
33 · Demand
Days 0–30: site, contracts, partner recruiting, founder outbound, five paid Sprints. 31–60: case studies, Build upsells, weekly Brief, partner directory. 61–90: retainers, standardised OS, first product wedge.
34 · Demand
Months 1–3 prove demand. 4–6 scale partner/referral and retainers. 7–9 formalise the issuer dataset and client portal. 10–12 test paid workflow software and premium market intelligence.
35 · Controls
Low-quality token clients, regulatory perception, claims failures, creator misconduct, payment disputes, partner quality, data exposure, dependency on a proposed rule, brand fragmentation. Counter: screening, written controls, evidence logs, fixed fees, counsel, one canonical domain.
36 · Direction
A reputable issuer-launch OS can expand into SaaS, data, a specialist marketplace, tokenisation advisory, launch intelligence and enterprise workflow. Do not anchor every claim to ICO fundraising.
37 · Delivery
Required: objective, owner, scope and exclusions, inputs, timeline, acceptance criteria, compliance triggers, KPIs. Issued within 24 hours of a qualified call. Deposit to start.
38 · Delivery
Scope the Sprint or Build as deliverables, not hours. Name exclusions in the same document. Acceptance is a read-out against the pack, not a fundraising result.
40 · Delivery
Entity, team, product evidence, token status, technical/security, legal, audience, brand, budget, named approvers. If those cannot be produced, work does not start.
41 · Delivery
Objectives, geographies, owners, response-time SLA, exclusions, claims discipline, partner needs, creator policy. Record the decisions in the workspace.
45 · Delivery
Segment by jurisdiction, sophistication and promotion route. “Global retail” is a control risk, not a target.
53 · Delivery
Identity, disclosure history, geographic reach, prohibited-claim record, payment terms, takedown clause. No roster seat without an archived policy.
66 · Demand
Product evidence, launch date, budget, counsel, token status, geographies, who decides. If they want RCA Pad to run a public sale, stop.
67 · Demand
One written proposal, two timed follow-ups, then close-lost. Do not renegotiate into percentage-of-raise or token-only pay.
78 · Demand
Stages: received, review, qualified, call, proposal, won, declined. Human review sits between score and calendar. No stage skips the screen.
89 · Controls
Pause the channel, pull the claim, notify the approver, archive the post, record the incident. Creator misconduct and unsubstantiated claims are stop-the-line events.
90 · Controls
Name the market before the message. UK retail-facing, US public offering language, and “global” socials are different routes. Uncertain route = pause.
94 · Controls
Every public page carries the boundary. Applications do not create a client relationship. This house is not legal, tax, investment or regulatory advice.
96 · Controls
What converted, what delayed delivery, what created risk, what should be standardised. If it cannot be assigned and measured, it is not yet an operating system.