Strawberry helps people working in Komos make sense of creator profiles, campaign briefs, deliverables, approvals, and performance updates. Gather the campaign context around a creator, identify delivery risks, prepare approval-ready feedback, and turn scattered campaign activity into a clear coordinator brief.
The work remains grounded in the signed-in Komos view, while consequential decisions stay with the person responsible for the account.
01
Begin with the live Komos work rather than a generic summary.
A useful Komos pass starts in the exact view where the team is already working.
Strawberry can read the current creator campaigns, isolate exceptions and open questions, and return a compact brief that points back to the underlying item.
02
Put the context around each Komos item where the owner can use it.
The detail needed to assess creator profiles, briefs, deliverables, approvals, and performance reporting often lives across tabs, documents, messages, and files. Strawberry can compare that surrounding evidence with the Komos item, distinguish confirmed facts from assumptions, and draft a recommendation that keeps its sources visible.
03
Turn a Komos exception into a precise proposal.
Spotting a komos issue is only the beginning of the work.
Strawberry can organise the relevant evidence, prepare a concrete correction or handoff, and show the expected effect before anyone changes the live Komos account.
04
Make the recurring Komos review match the real operating cadence.
Every Monday at 10:00, review active Komos campaigns for overdue deliverables, missing approvals, incomplete briefs, and creators waiting on feedback. Produce a campaign-manager pack; do not message creators or approve assets. A Komos-specific skill can retain the criteria, thresholds, and escalation path, so a scheduled routine produces a dependable operational packet rather than a vague status summary.
Yes. Sign in to Komos in Strawberry, then ask for a concrete reading, research, drafting, or preparation task grounded in that page.
It can navigate the signed-in Komos interface and prepare the proposed change. Review the affected creator profiles, briefs, deliverables, approvals, and performance reporting and expected outcome before approving anything that changes the live account.
Yes. Capture the exact Komos checks in a skill and schedule the review at the cadence the team actually works; actions that alter live data or reach other people should remain review-first.
Use only the intended Komos account, check every proposal against its live source, and deliberately approve any send, post, purchase, publication, or data change.