How We’re Testing Google Gems as an Early-Stage Leadership Team
Every early-stage founder, boutique agency owner, and consultant knows the exact same reality: you aren't just doing the work—you are playing every role in the go-to-market (GTM) lifecycle.
Before lunch, you have to act as the Sales Manager closing a deal. By 2 PM, you are the Marketing Lead trying to post on LinkedIn. By 5 PM, you are the Operations Director fixing a delivery bottleneck, and late at night, you become the CFO looking at margins.
Wearing all these hats simultaneously creates decision fatigue, breaks momentum, and stalls growth.
The traditional answer—"just hire a team"—isn't realistic when you are lean, testing ideas, or keeping overhead low. The modern alternative isn't sitting down every morning to type generic, one-off prompts into a blank, AI chatbot. Instead, it is constructing a persistent, specialized AI team inside your workspace.
At Statement Co., we treat AI as an ongoing operational experiment. We are actively testing Google Gems internally—not as a replacement for human judgment, but as a live sandbox for ideation, strategic co-creation, and operational leverage before we hire the larger team.
6 Roles to Help You Wear Every Hat
Instead of relying on a single generic AI prompt, we’ve been prototyping a modular library of Google Gems mapped to essential business seats. Here is the setup we are currently testing across the end-to-end GTM lifecycle:
Finance Lead & CFO: Tracks revenue goals, monitors margin floors, and keeps your time allocated to high-leverage business activities.
Product & Offer Lead: Challenges service delivery models, pressure-tests pricing, and helps design high-margin digital assets or extensions.
Operations & Systems Lead: Turns client delivery bottlenecks into standard operating procedures (SOPs), subcontractor scopes, and automated routines.
Storytelling & Marketing Lead: Synthesizes your raw ideas and industry notes into multi-channel campaigns, newsletters, and authentic positioning.
Sales & Commercial Manager: Reviews your pipeline, audits outreach angles, and crafts targeted connection hooks so you don't stall on outreach.
Leadership Team Meeting: Runs simulated 360-degree team debates across all roles to help you evaluate complex pivots before making a final call.
Tips to Set Up Your Initial Agent Team
Through our own trial and iteration, we’ve found that building an effective agent team requires treating each Gem like a new team member. By giving each tool explicit parameters, persistent files, and specific jobs, you can refine a setup that truly supports your workflow.
Use the Four-Pillar Prompt Framework: Structure custom instructions around Persona, Task, Context, and Format/Rules to ensure precise outputs.
Attach Core Knowledge Files: Upload persistent brand guidelines, SOPs, or offer specs directly to each Gem to eliminate repetitive background uploading.
Assign Dedicated Functional Roles: Build focused, single-purpose Gems (e.g., Sales Manager, SOP Builder) rather than one generic, all-in-one assistant.
Add a "Clarification First" Rule: Instruct your Gems to ask clarifying questions before generating answers if key details are missing from your prompt.
Establish an Operational Cadence: Assign specific functional Gems to recurring days of the week (e.g., Monday Finance, Wednesday Marketing) to maintain consistent business momentum.
The Weekly Cadence: Operating Your AI Team
An AI agent team is only as helpful as the rhythm you build around it. We’re working on dedicating specific days to engage specific functional leads keeps your focus clean.
Monday (Margins & Strategy): Input weekly numbers to your Finance Lead to check gross margins and set the week's priorities.
Tuesday (Offers & Innovation): Prompt your Product Lead to challenge current service packages and pitch non-consulting extensions.
Wednesday (Narrative & Marketing): Feed raw market observations to your Marketing Lead to build content and newsletter drafts.
Thursday (Sales & Pipeline): Run active opportunities by your Sales Manager to draft high-touch outreach hooks.
Friday (Operations & Systems): Audit delivery friction with your Operations Lead to build clean SOPs or workflow updates.
What Hasn’t Worked Across Our Tests
Of course, finding the sweet spot for these lightweight agents required plenty of trial and error—and a few failed setups along the way.
Overloading Instructions vs. Using Knowledge: We initially crammed background context, pricing tiers, and brand Voice guidelines directly into the Custom Instructions block. This ate up prompt real estate and diluted the core persona rules. Moving static reference material into attached Knowledge files made the Gems far more responsive to their primary directives.
Narrowing Scope Too Far: We initially built a CMO Gem with hyper-specific rules around tone and strict topic boundaries. However, restricting it too tightly stripped away its creative flexibility, leaving it unable to adapt when we asked for high-level campaign ideation or multi-channel pivots.
Broadening Scope Too Far: On the flip side, we gave a CRO Gem an all-encompassing mandate across sales, pricing, and pipeline forecasting. When tasked with analyzing our proposals, the prompt was too broad for the tool to pull and synthesize specific pipeline data, resulting in vague summaries rather than actionable revenue insights.
Building Too Many Agents at Once: We initially tried to deploy an entire 6-role executive suite simultaneously. Managing and refining so many moving parts at once created operational chaos and diluted our focus. Rolling back to perfect one agent at a time—getting its knowledge files, persona, and outputs completely dialed in before launching the next—made the overall system far more reliable.
Ask the Gem to Self-Optimize Instructions: When a Gem isn't delivering the expected output, don't keep rewriting the prompt from scratch. Instead, directly ask the Gem: "How should I update your custom instructions or knowledge files so you can perform this task accurately next time?" Let the AI audit its own boundaries and tell you where its context is falling short.
When to Bring in Strategic Partners
Testing AI tools like Google Gems early in your journey gives you the capacity of a broader team with limited resources. It helps you bypass blank-page paralysis, test offers quickly, and maintain positioning consistency. However, software alone cannot manage organizational change, navigate deep strategic ambiguity, or align human stakeholders.
However, as a company transitions into the growth and scaling phase, high-stakes decisions require strategic partnership to successfully navigate complex business pivots, align human teams and leadership, embed lasting change adoption, and orchestrate comprehensive go-to-market strategies across multiple channels.
When your business reaches the point where strategic complexity outpaces prompts, or when adopting new systems requires coaching and human enablement, bringing in a dedicated hire or partner like Statement Co. helps turn internal momentum into truly scalable growth.
