How it works · The full process
Every step, every design choice, the quality rubric, how we handle your material, and what we will not claim.
no surprises
at any step
01 / The process
You get in touch
The short form on the sample page asks for your name, email, organisation, and one line on what you want people to do differently. That is all we need to start.
We send you the full brief
A short structured document covering your goal and how you would measure it, who the learners are and their setting, the one behaviour change you most want, your source material, any boundaries, style references, and any other context. It takes about 15 minutes to complete. The brief is our qualification step; it keeps the build focused and the output useful.
You send your material
Documents, slides, a recording transcript, notes from a subject-matter expert, or a combination. The 48-hour clock starts when your material is complete and confirmed, not when you submit the brief. If anything is ambiguous enough to change the scope, we ask before starting.
Shaped around your people
Before any content is written, we read the brief against the source material. Who are the learners? What do they already know? What is the one behaviour the module must shift? This determines the opening, the depth, and where the try-it moments do the most work. The science name for this is calibration.
Your plan arrives, free, in 48 hours
A PDF: the strategy for the change you described, the gaps we found, creative ideas worth testing, and sample content where it helps. The 48-hour clock runs from the moment your material is confirmed complete. This is the free sample, complete in itself.
If you commission the build: from your material only
The module is built from what you send. Not supplemented with generic content. Not padded with examples from outside your domain. Every claim in the module traces back to your source. If your source does not support a claim, that claim does not appear.
Evidence-based design moves
The module is structured around four design moves, applied in this order: opening with an opening moment people recognise from their own work ( the science name for this is a worked example Worked example a step-by-step example from the learner's own context, before the abstract concept is named ); teaching in small chunks with core concepts separated and sequenced; quick try-it moments woven through the teaching ( the science name for this is retrieval practice Retrieval practice recalling beats re-reading; the effort of producing an answer from memory is what moves the idea from recognition to something you can use ) with process-level feedback rather than parked at the end; and application back to the learner's own work. Reminders and practice prompts over the weeks after are built into the module itself, so the follow-through is part of what gets delivered, not an add-on.
You receive the finished build
The commissioned work arrives ready to use, with every design decision shown alongside the content. Not a draft to finish. The reminders and practice prompts run as part of the programme, and we measure against the success criteria agreed in your brief.
02 / The quality rubric
Before delivery, each module is checked against four criteria. If a module fails any of them, it goes back into the build before it is sent.
The goal in the brief, the content of the module, and the practice tasks all point at the same behaviour. A mismatch between what the brief asked for and what the module teaches is a failure, not a trade-off.
The language, depth of explanation, and assumed prior knowledge match who the learners are. Structure that helps someone new can actively hinder an experienced practitioner. The brief shapes the content to your people at the start; the rubric check confirms it held that level throughout.
Quick try-it moments are placed at the point in the teaching where they do the most work, not parked at the end as a quiz gate. Reminders and practice prompts are spread across days and weeks, not crammed into a single sitting. Little and often beats one long session.
Every claim in the module is traceable to the source material you provided. No new claims are introduced. No statistics are cited that were not in your source. If a design move draws on published evidence, that connection is shown in the module's design notes.
four checks.
no exceptions.
your material
stays yours
03 / Confidentiality
Your source material is used only to build your module. It is not used as evidence for any claim Stica makes about its own capabilities. It is not shared with anyone else. It is not retained as training data, reference material, or a portfolio asset.
If you want your material deleted after delivery, ask and it is gone. We confirm deletion by email.
Used only to build your module
Never cited as evidence for Stica's claims
Never shared with third parties
Deleted on request, confirmed by email
The brief includes a boundaries section. Anything you flag as out of scope does not appear in the module. Approval is part of the build, not an afterthought.
04 / What we will not claim
These limits are not hedging. They are the line between what the evidence supports and what it does not. Saying them out loud is part of how Stica works.
We do not promise measured behaviour change from a single sample. No single piece of content can guarantee that, and saying otherwise would be dishonest. What we do promise is a module designed and checked against an evidence-based rubric, so when a learner picks it up, it has been built to give the learning a genuine chance.
this honesty is the pointwhat the evidence
supports. no more.
Ready?
Two minutes to get in touch. We send you the full brief. The clock starts when your material arrives.
Get the free 48-Hour Sample