AISC / The launch method
AISC Launch Playbook.
From a working demo to a coordinated creator launch. Six stages, with the decisions, inputs and approvals that keep the product story grounded.
Brenz Hills · Co-founderBeyond launch day
One release.
More ways into the product.
The announcement opens the conversation. Creator demos, practical answers and new use cases give the product more entry points over time.
Announcement
Creator demos
Useful follow-ups
One story. Six connected stages.
A working product, a clear audience and a reason to care. The sequence adapts to the release, not an algorithm promise.
01 / AISC
Define the launch
Start with the action, not the view target. An AI demo, a developer tool and a gaming launch need different audiences and different next steps.
- What you get
- A campaign direction connecting one audience, one product story and one primary action.
- From your team
- A working demo, product access, target market, intended date and any known limitations.
- Before moving on
- The objective, landing destination and what counts as a useful result.
02 / AISC
Match the creators
Audience fit comes before follower count. Recent content, subject knowledge and the quality of replies matter as much as reach.
- What you get
- A proposed creator selection with a rationale for each audience and content angle.
- From your team
- Priority languages, examples of relevant users and any conflicts or exclusions.
- Before moving on
- Creator selection and scope before outreach and bookings are finalized.
03 / AISC
Brief and test
Creators need to try the product, not repeat a script. Separate verified capabilities from roadmap ideas and leave room for their own voice.
- What you get
- A product brief, demo references, supported claims and disclosure guidance.
- From your team
- Test access, someone who can answer technical questions and approved brand materials.
- Before moving on
- Product facts, demo accuracy, links and paid-partnership disclosures.
04 / AISC
Publish and participate
The original announcement anchors the launch. Creator posts add distinct demos and perspectives, while your team handles product questions.
- What you get
- A proposed publishing sequence, destination links and clear conversation owners.
- From your team
- The original announcement, available support and a ready landing page.
- Before moving on
- Publishing sequence, final factual checks and who answers which questions.
05 / AISC
Follow the questions
Use real replies to decide what comes next. A new use case or a clearer demo is more useful than repeating the same announcement.
- What you get
- A follow-up outline built around questions, objections and relevant use cases.
- From your team
- Product updates, support feedback and any available activation data.
- Before moving on
- Follow-up angles and any additional content scope.
06 / AISC
Separate reach from results
Views are exposure, not signups or GitHub stars. Report social performance separately from product actions and be explicit about attribution gaps.
- What you get
- Published links, available social metrics, measured product actions where available and learnings for the next launch.
- From your team
- Analytics access or exports, the measurement period and agreed conversion definitions.
- Before moving on
- The reporting period, sources and any results cleared for public use.
From the playbook to the timeline
See the published campaigns behind our approach.
Explore case studiesWhat are you launching?
Tell us the product, audience, target date and the action you want people to take.
Launch with AISC