Every week
News feed
What changed in your AI tools, with a badge that says whether you can use it here yet.
See the News feedAI champion networks for companies of any size
Grovework builds and runs the network of employee AI champions that turns licenses into daily use, across every AI tool you pay for, without reading anyone's prompts. Start with a 90-day pilot, then run it yourself or keep us running it.
Usage metadata only. We never collect prompts.
Fig. 1A grove in cross-section. Above ground, separate trees. Below, one network. Champions sit where the roots meet, and each one reaches the colleagues around them.
The problem
Most rollouts follow the same arc. Seats get assigned, the launch webinar fills up, and a handful of enthusiasts take off. Everyone else tries it twice and goes back to the old way of working.
What changes habits is a trusted colleague on each team who shows how AI fits the work in front of them, and keeps showing up after launch week. That takes a network with a calendar, a selection process and a report. Grovework builds and runs all three.
85%
of enterprise employees aren't using AI to drive business value, according to Section's January 2026 research.
60 to 90days
is how quickly champion networks stall without a steady rhythm, in the experience of a CISO writing for CSO Online.
Practitioner view: CSO Online, Nov 2025 ↗
Why a grove
Trees in a grove are linked through their roots and shared fungal networks that move water, nutrients and even warning signals from tree to tree. Ecologists sometimes call it the wood wide web.
A champion network does the same work for AI know-how. It connects people across teams in a way the org chart never shows.
How it works
Five parts of one cycle, plus two that run alongside it. Champions work in Slack or Teams. Your program lead works on the web platform.
Pick your AI tools and goals, then choose programs from a menu.
Nominations come in, and a recommended slate comes out each quarter.
The steady rhythm that keeps a network alive past launch.
Ideas from teams come back to them as tools they use.
Show leadership what changed, team by team.
Steps 2 to 5 repeat every quarter
Plus two parts that run alongside the cycle
Every week
What changed in your AI tools, with a badge that says whether you can use it here yet.
See the News feedEvery quarter
Energy, carbon and water estimates for your AI use, habits that cut waste, and verified restoration you can fund.
See sustainable adoptionThe Grove Loop
Networks stick when ideas from teams ship back to those teams. Grovework connects teams, champions and builders, sends each idea down the shortest path, and closes the loop with the person who raised it.
Fig. 2The Grove Loop. Anyone plants a seed from Slack, Teams or the web by saying what slows them down and how often. Each seed ends as a solution the team uses, or as a quick answer when one already exists.
Three paths an idea can take
The champion finds a feature or solution you already have and answers with a Try this guide. Nothing gets built.
Who answersThe team's champion
No-code work inside tools you already approved, such as custom GPTs, Copilot agents, Gemini Gems and Claude projects.
Who buildsChampion builders
Anything that needs company systems, data or code. The shaped request goes to the people who build those.
Who buildsTechnical buildersCentral AI team, IT, data, engineering
Every builder has a profile with platforms, skills, approved data access and monthly capacity. Cedar matches each request on those, and Linden groups similar seeds from different teams so one build serves all of them.
Review that scales with risk
One person's tool. No review, and it follows your AI use policy.
Shared with a team. The champion lead checks data and ownership.
Connects to company systems, uses sensitive data or faces customers. The builder team reviews it, and IT security, privacy and risk sign off.
One idea, seed to tend
Seedfrom Teams
An analyst answers two questions. What slows you down? Explaining purchase order discrepancies to vendors.
How often? Every day.
Shape3 days
The team's champion finds nothing in the solution catalog that fits, estimates the hours at stake and picks a champion build.
BuildTeam review
A champion builder makes a Copilot agent that drafts each explanation from the purchase order, receipt and invoice.
Plant2 teams
Ships to 2 teams with a launch kit, joins the solution catalog, and Aspen posts it to the news feed.
Tend30-day check-in
Confirms 18 hours a month saved. Aspen tells the analyst who raised it.
Fictional team and figures, for illustration only.
Aspen writes them an update from seed to check-in. Rowan flags seeds that wait too long, against targets of a champion reply within 5 business days and a build decision within 2 weeks.
They stay in Jira, ServiceNow or Azure DevOps. Grovework creates the ticket with the shaped request and syncs status back, so nobody keeps a second backlog.
Grovework stores solution metadata only, such as name, owner, tool, risk tier and link, and never prompts or code.
Champion selection
Most programs take whoever volunteers first. Cedar weighs six signals and recommends a slate that covers the teams that need help most. Selection never looks at the content of anyone's prompts.
Each slate is checked for a mix of function, level and location before it reaches you.
Cedar's recommended slate
Three peer nominations. Her manager confirmed 3 hours a month.
Support has 140 licensed users and no champion yet.
Her team's weekly use is climbing. Two colleagues named her.
Adds a champion outside headquarters.
Fictional names. Covers 3 teams with no champion today.
You make the final call.
Terms
1 to 2 quarters
Each champion serves a set term with a clear end date, which makes the role easier to say yes to.
Rotation
About a third
of the network is refreshed each quarter. New people arrive while most of the group carries on.
Alumni
Alumni pool
Past champions stay on call for sessions, mentoring and the next pilot.
Meet the helpers
A network runs on a hundred small tasks. Aspen, Cedar, Linden and Rowan, each named for a tree that grows in groves, draft, sort and chase, so your program lead can spend time with people.
Drafts charters, launch announcements, session agendas, reminders and the weekly news digest. Updates whoever raised an idea at each stage of the Grove Loop.
“Starting in March, every team will have an AI champion: a colleague with time set aside each month to help you get more from the tools.”
Recommends each quarter's champion slate, explains why, and manages rotation. Matches each seed to a builder by platform, skill and capacity.
Suggest Marcus B. for Customer Support. No champion on the team yet, and his manager confirmed 3 hours a month.
Writes the quarterly report, including the sustainability page, and spots trends. Groups similar seeds so one build serves several teams.
Q3 report drafted: adoption by team, solutions planted, hours saved, and two teams to watch next quarter.
Flags stalled teams, missed sessions, coverage gaps, overdue rotations, seeds waiting too long, and usage spikes that push the footprint up.
Customer Support hasn't held a session in 6 weeks.
Helpers draft, recommend and flag. Your program lead approves what goes out.
Stay current
Champions hear one question more than any other. “I read this tool can now do X. Can we use it here?” The News feed answers it in one place.
Every outside item carries a badge
Vendors announce features faster than companies approve them. Your program lead or IT sets the badge, so champions stop guessing and nobody builds a habit on a feature that hasn't been cleared.
New features come with a short “Try this” exercise, and the “I tried it” count feeds the proficiency layer of your report. Each week Aspen drafts a Slack or Teams digest by tool, department and role, and your program lead approves it before it goes out.
News feed
Example release: meeting recap options. Recaps can group action items by owner. IT switched this on for Finance last week.
Try thisOpen last week's close meeting recap and ask for the action items grouped by owner.
Source link: vendor's official note
Example release: shared project spaces. Teams can keep files and instructions in one place. IT is checking where those files are stored.
Source link: vendor's official note
Example release: longer document uploads. Larger files fit in a single conversation. Announced by the vendor and not yet checked here.
Source link: vendor's official note
Example release: personal cloud storage. Would let people attach files from personal accounts. Use the company drive instead.
Source link: vendor's official note
Priya N., Accounts Payable. Built a prompt that drafts vendor follow-up emails from the aging report. Her team now runs it every Monday.
Demo data. Generic example items, not real vendor announcements, and source links are placeholders. Names are fictional.
Measurement
The headline view compares teams that have an active champion with similar teams that don't. Usage comes from the admin reports your AI tools already produce.
Weekly active share of licensed users
By month since the network launched
Fig. 3Illustrative data showing the shape of the headline view. Not a client result.
| Month | With a champion | Without one |
|---|
Five layers in every report
Active users and depth of use by team, trended against teams without champions.
Pulse checks and training completion.
Coverage, attendance, people helped, and rotation on schedule.
Seeds planted, time from seed to plant, reuse across teams, and confirmed hours saved.
Confidence and trust in AI, from short pulse surveys.
Using the Grove Fund? Linden adds a sustainability page with footprint ranges and certificates retired. See how it works
Your data stays yours
Grovework never collects prompts, responses or files. Adoption comes from the aggregate usage reports your AI tools already give admins, shown by team. Every client starts without giving us any system access.
Champion names, work emails, departments, survey answers, seeds and solution metadata.
No connection to your AI tools
Aggregate usage exports from your AI tools' admin consoles, uploaded monthly.
No system access
Every client starts on Tier 0 or Tier 1
Read-only connections to your tools' admin reporting, in place of manual uploads.
Read-only, reporting APIs only
Grovework runs in an environment you host and control.
Data never leaves your environment
Adoption is reported by team, and groups smaller than 5 people are never shown on their own. A report never reads as monitoring individuals.
Prompts, responses and files never reach Grovework. Champion selection never looks at what anyone typed.
Employee IDs can be pseudonymized with keys your company controls.
You can delete everything Grovework holds about your company, at any time.
Opt-in onlyIndividual usage data is used only for champions who choose to share it.
Grovework runs the people side of adoption. Your AI tools stay as they are, and you can mix them or switch later without rebuilding the network.
Sustainable adoption
Sooner or later someone asks what your AI use costs in energy, carbon and water. Grovework estimates it from the usage data we already have, helps champions cut the waste, and runs the Grove Fund so your company can pay for verified restoration. Your sustainability team gets an answer for AI in their Scope 3 reporting.
Energy, carbon and water, estimated from usage you already share.
Interactions, tokens or spend by tool and team. Every figure is a low, central and high estimate with its data quality labeled.
Champions teach habits that cut waste without cutting use.
A right-sized model for each task, with reasoning, image and video generation saved for work that needs them. Rowan flags spikes, and Linden shows footprint per hour saved.
The Grove Fund turns a rule you set into verified restoration.
Per 1,000 AI interactions, per licensed seat each month, or a share of AI spend.
A quarterly sustainability page in Linden's report.
Method, ranges and certificates retired, with figures ready to export for Scope 3 reporting.
AI footprint for one quarter
Example company · 1.2 million AI interactions
Central estimate 1,200kWh
360 to 3,600 kWh10x spread
Central estimate 480kg CO2e
36 to 1,440 kg CO2e40x spread
Central estimate 12,000Labout 3,200 gal
360 to 54,000 L150x spread
Covering the high water estimate takes 15 Water Restoration Certificates at 1,000 gallons each.
Fig. 5Illustrative. Demo factors per interaction, applied to 1,150,000 text interactions and 5,000 images, each image counted as 10. Bar length shows the spread from low to high on a log scale. Not a client result.
Spend-basedUsage-basedProvider-reported
Published per-prompt figures differ by more than 100x on water, because they count different things.
0.26mL
of water for a median Gemini text prompt, as Google reports it, counting data center cooling. Google also reports about 0.24 Wh and 0.03 g CO2e. Not independently verified.
45mL
of water for a 400-token response in Mistral's lifecycle study, which also counts electricity generation and hardware. It reports 1.14 g CO2e.
Both can be right about what they measure. So Grovework never shows one precise-looking number. Every estimate carries a low, central and high value and a data-quality label, and the method is published and updated as AI providers disclose more.
Step 3 in detail
Your company sets a contribution rule, and the fund pays for verified restoration against it. Grovework tracks every purchase and reports what was retired.
Pick a rule
1 certificate = 1,000 gallons restored. Third-party verified and registered.
Credits for carbon removed from the atmosphere, verified and bought from vetted partners.
A visible layer for employees, with one tree per solution planted through the Grove Loop. Kept separate from any carbon claim.
Guardrails
“We funded restoration of 48,000 gallons.”
“Our AI use is carbon neutral.”
Water Restoration Certificates back water claims only. Carbon claims need carbon removal credits.
You buy from vetted partners directly or through a partner's purchasing API. Grovework tracks and reports what was retired.
Our footprint method is public, and we update it as AI providers disclose more.
Ways to work with us
We run your champion network with you for one quarter, across every AI tool you pay for, against measures agreed at kickoff. After that, keep us running it or take it over yourself.
Grovework runs the network with your program lead for one quarter.
Fixed price, shared on a call
Ask about a pilotAfter the pilot, Grovework keeps running the network alongside your program lead.
Pricing on request
Ask about managedYour own program lead runs the network on Grovework.
Pricing on request
Ask about the platformPriced by the number of people with AI licenses. Bundles cost less than adding modules one at a time, and sustainability is free in every plan.
The core network. Small enough for teams under 250 AI users.
Seedling plus the Insights pack.
Costs less than adding Insights on its own
Everything, including the Grove Loop.
Insights pack included at no extra cost
The Grove Fund is free in every plan. Footprint estimates and contributions never cost extra, because sustainable AI adoption should be the default. Purchases go to vetted partners with no markup.
Our starter library of session agendas, launch messages, challenge briefs, role descriptions and checklists, plus a launch plan built from your own exports. Pricing on request.
For mature networks. Turn proven solutions from the Grove Loop into reusable AI skills that teams can run in their own tools. Pricing on request.
Who we are
Our founder built and scaled AI champion programs inside a large enterprise, and learned what keeps them going after launch week: a steady calendar, fair rotation, and reporting that leadership believes.
Grovework turns that experience into a platform and a service that run on any AI tool. He draws and paints, and he drew the Grovework logo.
Questions
Talk to us
Tell us where your rollout stands. We'll set up a first conversation about your goals, your tools, and whether a managed network or the platform fits.
Thanks. We'll be in touch to set up a first conversation.