File Name Generator
Generates standardized names per the RTS file naming SOP. Fields marked * are required.
File Details
Codes are auto-uppercased. Spaces in descriptions convert to hyphens automatically.
Spaces → hyphens automatically. ~60 chars max.
Generated File Name
Fill in the fields above to generate a file name
Naming Convention
YYYY-MM-DD_Client_Service_Description.ext
YYYY-MM-DD_
ClientCode_
ServiceCode_
Description.
ext
Rules Reminder
Hyphens in descriptions — never spaces
Extension always lowercase (.pdf not .PDF)
Add -v2, -v3 when updating existing files
Add -DRAFT for work-in-progress files
Description readable to anyone on the team
Service Code Quick Ref
Destination URL *
Select a client to auto-fill. Edit when linking to a specific subpage, event, or landing page.
google
facebook
instagram
email
linkedin
cpc
email
organic
social
referral
Lowercase + hyphens. Auto-prefilled with client slug when a client is selected.
Paid search keywords only.
A/B test differentiator.
Add UTM tracking
Append utm_* parameters to the destination URL.
Shorten the URL
Creates a tracked rtslink.co short link.
Generated URL
Fill in the required fields above
Select a client above to enable ClickUp save
ClickUp Name Generator
Generates names for ClickUp docs, pages, lists, folders, and tasks per the ClickUp Naming Conventions SOP v1.2. Different from file naming — ClickUp items are client-first.
Item Details
Pick the item type, then fill the relevant fields. Topic auto-formats to CamelCase.
Auto-formats to CamelCase. Leave blank if the category alone is descriptive enough.
Generated Name
Fill in the fields above to generate a name
Format — Doc / List / Folder
[CLIENT]_[Category]_[Topic]
CLIENT_
Category_
Topic
Example: AOV_EmailTemplates_B2B
Convention Rules
Client-first format — opposite of file naming SOP
CamelCase or PascalCase — no hyphens or spaces
Sub-brand prefix only when item is unambiguously about it
Pages inside docs don't repeat the client prefix
Tasks are verb-led, no client prefix in context
Sub-brand prefixes for AOV: JA, IGC, NRP
Subpage Suffixes (StrategyHuddles)
YYYY-MM-DD — Strategy Session (no suffix)
_Psychology — Founder Psychology Session
_GapReport — BVS Gap Report Session
_90Day — 90-Day Review check-in
Proposal Generator
Drafts a Tier 1 proposal from discovery call notes. Two passes — Sonnet scopes the engagement and suggests line items, then Opus writes the full proposal once you've confirmed scope and pricing. Required fields marked *.
1
Discovery input
What you learned from the call. Sonnet uses everything here to scope the engagement and pull line items from the service catalog.
Free-typed name is fine — registry is optional.
Picking a registry entry fills the company name and website.
The person who will receive this proposal.
Specific descriptor of what they want.
Be specific — these become Pass 1 line items.
Fill the required fields to enable Suggest line items
2
Review & edit
Two scoping options come back. Edit anything before generation — line items, prices, scope, payment structure.
Run Step 1 to see line items.
3
Generated proposal
Streams as Opus writes. Copy by section or download as markdown.
Confirm scope and prices in Step 2 to generate.
How this works
1
Sonnet 4.6 reads your discovery context and returns two scoping options with line items, market rates, and dual pricing. ~5–10s · ~$0.02
2
You edit line items and prices, then pick the option to send. Floor pricing stays internal.
3
Opus 4.7 writes the full proposal section by section, streaming as it goes. ~30–60s · ~$0.30–0.50
Dual pricing
Suggested investment — what the proposal leads with. 30–50% below market high, rounded.
Minimum investment — your negotiation floor. 70–75% of suggested. Internal only — never appears in proposal copy.
Prepared by
Required by Pass 2 for the closing line.