How2Socials
Social growth platform: Custom CPTs, reusable landing blocks, and owner-editable foundation.
00 // Interface Preview
Desktop and mobile references
01 // Snapshot
OperatorCreator teaching social growth
Was BrokenNo real site; ideas lived in posts and decks
ChangedClean WordPress build with CPTs, landing pages, and owner controls
TrajectoryLaunches happen in hours, not days, with one person editing
02 // Verdict
Strong brand and offers but no working site to anchor them. Audience came from socials; needed a home for programs and proof. Wanted simple blocks owner could extend without calls.
03 // Structural Constraints
No StructureNo structure for services, testimonials, or lead magnets
Launch FrictionLaunching offers meant rebuilding pages from scratch
Vendor Lock-InNeeded future-proofing without a maintenance retainer
04 // Leverage Moves
CPT LibrarySet up CPTs for programs and testimonials so content stays uniform
Landing SystemBuilt reusable landing blocks tied to email capture flows
Design TokensDialled in palette, spacing, and typography for mobile first
Edit GuidesLeft short edit guides so owner can ship without us
05 // Evidence
Fast LaunchesClean launch that loads fast and reads well on phones
Program PublishingNew programs and testimonials publish without touching layouts
Zero Monthly CallsOwner ships updates solo; no monthly calls or tickets
06 // Ruled Out
Custom PlatformCustom platform build (WordPress with CPTs sufficient and maintainable)
Heavy CRMsHeavy CRM integrations (email capture sufficient for this scope)
Retainer RequiredMaintenance retainer required (owner editing removes this dependency)
07 // Before / After
BeforeNo site; offers and proof scattered across socials
AfterWordPress with CPTs, reusable landers, and simple edit guides
08 // Decision Log
CPT ArchitectureAstra and Elementor with CPTs for programs and testimonials
Email Capture FlowReusable section library tied to email capture and tagging
Schema InheritanceSchema and meta templated so new pages inherit SEO basics
09 // Irreversible Outcomes
Content ArchitectureCPT library provides scalable content architecture
Reusable SystemReusable landing blocks eliminate rebuild friction
Owner IndependenceOwner publishes without developer dependency
10 // Status
Live and easily extendable.
Role: Technical Lead / Developer.
Mandate: Flexible growth path, owner editing, CPT architecture.
