Start with media briefs, then build from there.
Gooden Group came to Benali with a clear first workflow: automate the preparation work inside media brief production. The proof of concept showed how that can work across article links, source text, tagging, and brief formatting.
This proposal answers that request with two production paths. The goal is to make the daily brief workflow faster and more consistent while keeping Gooden Group's review and client-facing judgment in the loop.
It can also be the first proof point for a broader AI partnership. Once this workflow is working, the same approach can help Gooden Group decide where AI should support other recurring work, handoffs, client context, and internal operations.
Choose the right production path.
The proof of concept can become a lightweight AI skill or a purpose-built application. Both can prepare briefs, preserve source text, connect approved Gooden Group context, and keep review visible before client delivery. The right choice depends on how much control, interface design, integration, and reporting Gooden Group wants in production.
Claude skill
A guided workflow inside Claude that takes approved inputs, follows Gooden Group's brief rules, and produces a reviewed draft in the team's format.
- Brief generation from pasted article links and client context.
- Gooden Group templates, aliases, formatting rules, and review prompts.
- Publisher handling guidance for the sources used in the proof of concept.
- Output ready for team review before client delivery.
- Fastest way to turn the proof of concept into a repeatable workflow.
- Lower first investment and easier to adjust as the process changes.
- Best if the team is comfortable working inside Claude.
- Requires Gooden Group users to use Claude for the workflow.
- Less control over interface, roles, reporting, and automated handoffs.
- Best for pasted links and guided runs, not a full internal product.
Custom app
A purpose-built media brief application with a simple interface for sources, client profiles, draft status, review, and output control.
- Simple web app for entering clients, article links, and brief details.
- Draft generation, source text preservation, review states, and formatted output.
- Client aliases, templates, publisher notes, and team workflow rules.
- Admin-friendly path for updating templates and source handling after launch.
- Cleaner daily experience for users who do not want to work inside Claude.
- More control over interface, permissions, history, and future integrations.
- Better foundation if media briefs become a core operating system.
- Higher first investment and more scoping decisions up front.
- Requires choices around hosting, sign-in, data storage, and permissions.
- Best when Gooden Group wants a durable tool, not just a guided workflow.
The Claude skill is the strongest starting point because it keeps the investment focused while Gooden Group learns what the daily workflow actually needs in production. If the team proves the workflow is valuable but wants a cleaner interface, review status, history, permissions, or reporting, that learning can guide a custom app instead of guessing up front.
Optional add-ons
The recommended skill path covers the core daily workflow. These add-ons are scoped separately so Gooden Group can decide what belongs in the initial production build and what can wait until the workflow is in use.
Monitoring imports and APIs
+$2-4K- Pull links or exports from approved monitoring sources instead of relying only on pasted URLs.
- Best when the daily workflow needs less manual setup before brief generation.
Correctness and sentiment checks
+$1-3K- Add extra checks for missing source details, unsupported claims, and brief quality flags.
- Include sentiment or coverage classification when it helps the team review faster.
Email, archive, and handoff
+$1-3K- Create a cleaner path from approved brief draft to Gmail or Outlook.
- Preserve final briefs, source text, and review history for later reference.
Reporting and analytics
+$2-4K- Show volume, publisher reliability, review flags, client coverage patterns, and workflow usage.
- Best once the team knows which metrics are useful after launch.
Broader partnership support
Managed AI Ops is broader ongoing support, not a required add-on to the media brief build. In the wider AI partnership, the Managed tier at $2-4K per month can cover this workflow plus future deployments: tuning, publisher handling, template updates, permission review, small improvements, adoption support, and ongoing system care after launch.
AI workflow deployments need operating judgment, not just automation.
This build is not only about making AI generate a brief. It needs the judgment to decide what should be prepared, routed, drafted, checked, reviewed, and kept under Gooden Group's control.
Operating judgment
We shape the workflow around how the team actually prepares client-facing briefs, where review matters, and where uncertainty needs to stay visible.
Practical AI workflow design
We design prompts, skills, tool calls, source handling, review states, and system boundaries so AI supports the workflow instead of blurring responsibility.
Built around the operating layer
Templates, publisher sessions, client aliases, email drafts, archives, analytics, and monitoring outputs need to connect deliberately.
Speed without losing trust
AI helps the workflow move faster, but quality still comes from clear boundaries, review paths, source traceability, testing discipline, and ongoing tuning.
Finalize the workflow, then test it against real briefs.
Because Gooden Group has already walked through the flow and seen a proof of concept, the next step is lighter weight. We need more examples, a clear list of edge cases, and agreement on the exact workflow design before we turn it into a production tool.
- Collect real examples. Review recent briefs, source links, final templates, edge cases, and examples of what the team changes before sending.
- Identify edge cases. Clarify publisher access, paywalls, missing article text, social and broadcast inputs, client aliases, review flags, and exception handling.
- Finalize workflow design. Agree on the selected path, inputs, draft format, review moments, handoff, and which optional add-ons belong in the production build.
- Build the production workflow. Turn the approved design into the selected skill or app with review controls, source handling, and draft output path.
- Test and tune. Run real examples through the workflow, adjust prompts and rules, and confirm the result matches Gooden Group's client-ready standard.
- Launch and maintain. Roll out to the right users, document the system, and keep Benali accountable for improvements and fixes.
Fast work still needs the right access.
This project moves quickly if the business inputs are available early and the decision path is clear.
Decision owner
A Gooden Group owner available for scope choices, review boundaries, tradeoffs, and launch decisions.
Real examples
Sample briefs, edge cases, final templates, and examples of what the team changes before sending.
System access
Approved access to client aliases, publisher list, monitoring exports or link sources, and email draft path.
Internal expert
A Gooden Group subject-matter expert available to clarify how media brief work really happens.
Next step: edge cases and workflow design.
If the media brief workflow is the right first project, the next step is a focused working session to review real examples, identify edge cases, confirm the selected path, and agree on the production workflow design. After that, we can finalize the number and start the build.