# Automation Advisory: AI workflows your team owns in 2–3 weeks One fixed-scope project per capability: built for your internal marketing team, handed off with training, fixed price quoted at discovery. The only engagement with no prerequisite. ## Who Advisory is for An AI marketing automation service usually means one of two things: a tool subscription that automates someone else’s workflow, or a consultant who recommends one. Advisory is neither. It is a fixed-scope project that builds one specific capability, installs it in your team’s hands, and ends. It fits three situations. ### Your marketing team is busy, and one capability is missing. Briefs take a day to write. Competitor tracking is manual. Reporting eats every Friday. You don’t need outsourced execution; you need that one workflow built, documented, and owned by your team within weeks. ### You finished the Sprint or the retainer, and the system needs to grow. The transferred setup runs. Now you want a new agent, a deeper integration, or another person trained on it. Advisory extends what you already own, whether it came from the Strategy Sprint or the retainer. ### You want AI-driven marketing automation without outsourcing marketing. Your team keeps strategy, voice, and publishing. We build the production machinery they run. The capability compounds in-house instead of accruing to a vendor. ## What an Advisory project covers Every project is scoped to a single defined capability, written into the Statement of Work as an acceptance test. Four engagement types cover most of them. ### Custom skill development. A repeatable workflow codified as a skill your AI setup runs on demand: competitor content tracking, brief generation from a keyword, page drafts checked against your templates. Built on your data, tested against your real cases. ### Claude Code setup for your marketing team. Onboarding, permissions, a skill library matched to your stack, and the instruction set that keeps output consistent across everyone who uses it. ### Workflow integrations. Connections between the AI layer and the tools your team already lives in: Slack, analytics, CMS, GitHub. The automation lands where the work happens, not in another dashboard. ### Team training. Working sessions that teach your team to run, extend, and maintain the AI-augmented workflow. Documented, recorded, and built around your actual tasks rather than generic prompting advice. ## Commercial terms ### Fixed price, quoted at discovery. Scope is defined before the quote, so the quote is a number, not an estimate. No hourly billing, no scope drift. ### Single invoice on completion, net-14. You pay when the capability works, not when the project starts. One Statement of Work, signed before the build. ### 2–3 weeks, calendar-committed. The timeline is in the SOW, not in a pipeline queue. ### No prerequisite. Advisory is the one engagement you can start directly. Sprint or retainer history shortens scoping but is not required. ### Runs in your environment. The capability is built in your own Claude Code workspace, under your accounts and API keys, with budget limits set during the build. Model usage stays on your subscription: no pass-through billing, no markup. ### Pilot terms. The first clients work at reduced terms in exchange for a publishable case study. Ask during discovery. ## Yours at project end - The skill or automation - Its documentation - The integration configs - The scripts - The updated instruction set (CLAUDE.md) ## What teams ask before an Advisory project **How is this different from hiring a developer or an automation freelancer?** A developer builds what you specify; an AI marketing consultant recommends what you should want. Advisory closes both gaps: we run the same automations in production for our own engagements, so the project arrives with the marketing logic already in it. The scope is an acceptance test, the price is fixed, and your team is trained on the result before we leave. **Do I need a Strategy Sprint before an Advisory project?** No. Advisory is the only tier with no prerequisite. A capability does not need a full strategy behind it; it needs a clearly scoped workflow and an owner on your team. If we have already run a Sprint or a retainer with you, scoping is faster because the dossier and the setup exist, but neither is required. **How is the price determined?** By scope, fixed before the build. Phase 1 defines the capability as a testable outcome in the Statement of Work; the quote follows from that definition. One invoice on completion, net-14. If discovery shows the scope is larger than one project, we say so and split it rather than letting one engagement drift. **What if we want ongoing maintenance?** The handoff is built so you don’t need it: documentation, training, and code under your accounts, plus a 90-day support window that covers breakage from API or model updates at no cost. Extensions and new capabilities become new fixed-scope projects. If what you actually need is continuous production rather than maintenance, that is the retainer, and we’ll tell you so at discovery. **Can you train the whole marketing team?** Yes. Team training is one of the four engagement types, and it scales from one owner to the full team, in-house or fractional marketing teams alike. Sessions are built around your actual workflows, recorded, and backed by documentation, so people who join later onboard from the materials rather than from scratch. **Do you build custom integrations with our existing stack?** Yes, within the marketing workflow: Slack, analytics tools, CMS, GitHub, and the data sources your reporting depends on. We need API access and a technical contact on your side. What we don’t build: paid advertising management, email automation, or integrations unrelated to the capability in scope. ## Ready to start with an Advisory project? A 30-minute discovery call: we audit the target workflow, define the capability, and quote the fixed price. If one project can’t cover it, we say so on the call. --- Source: https://thehine.ai/services/automation-advisory Last updated: 2026-06-10