Pick a simple monthly amount
Start with a number your company can explain in one sentence. It can be small; the point is repeated personal use, not a flashy perk.
How it works
A personal AI budget, with enough structure to launch safely.
The Tinker Pledge should feel simple to employees and legible to the people approving it. Set the budget, define the boundaries, and keep the policy light enough that curiosity still does the work.
01 · Budget design
Make the benefit easy to understand.
The best version is boring to administer and generous in spirit. People should know what they can spend, how they get reimbursed, and what is outside the line.
Use lightweight reimbursement
Treat it like a recurring benefit with a simple reimbursement path and a curated starter list. Keep exceptions possible, but make the default easy.
Offer it broadly
AI fluency is not only for technical teams. The benefit is strongest when operations, recruiting, design, sales, support, and leadership all get reps.
02 · Guardrails
Give freedom without making the policy vague.
Keep company data out
Make the boundary explicit: personal tools are for personal use, public information, and low-risk experimentation unless a tool is approved for company data.
Do not turn it into surveillance
No usage reports, prompt reviews, or productivity scorekeeping. The company funds fluency; people keep their private life private.
Check payroll and tax treatment
Review the benefit with your finance or payroll partner before launch. Different companies and locations may need different handling.
03 · Starter tools
Keep the page compact and the policy flexible. The catalog is a launch default people can browse, search, and improve over time.
A browsable list, not a giant directory.
Familiar first
Start with names people recognize.
Employee-led additions
Let usage show what belongs next.
Clear data boundary
Personal tools stay for personal practice.
Review quarterly
Keep the budget stable while the list evolves.
Browse the starter list
Browse the starter list by category, or search for a familiar name or use case.
18 tools
ChatGPTThink & askDraft, plan, explain, summarize, and brainstorm.ClaudeThink & askWork through writing, analysis, documents, and code.GeminiThink & askExplore ideas, ask questions, and get help across everyday tasks.PerplexityResearchSearch, compare sources, and chase down unfamiliar topics.GrammarlyWrite & organizePolish messages, drafts, and everyday writing.Notion AIWrite & organizeTurn notes, plans, and docs into clearer next steps.GitHub CopilotCode & buildPair on code, scripts, and personal technical projects.CursorCode & buildBuild and refactor inside an AI-native code editor.Claude CodeCode & buildDelegate coding tasks from the terminal, IDE, web, or desktop.Replit AgentPrototype appsTurn an app or website idea into a working project in the browser.v0Prototype appsGenerate and iterate on web apps, interfaces, and prototypes.BoltPrototype appsBuild websites, apps, and prototypes from a chat prompt.LovablePrototype appsCreate apps and websites by chatting with AI.MidjourneyCreateExplore visual ideas and generate image concepts.Canva Magic StudioCreateMake quick graphics, presentations, and design drafts.RunwayCreateExperiment with AI video, images, and motion.ElevenLabsVoice & mediaCreate voice experiments, narration, and audio ideas.DescriptVoice & mediaEdit podcasts, videos, and transcripts with AI help.
04 · Rollout
Launch it in weeks, then improve it from signal.
Avoid turning the launch into a platform selection project. Start with a clear budget and policy, then adjust once people show you what they actually use.
- 01
Name the budget and owner
Choose a monthly amount, decide who owns reimbursement, and write the one-paragraph policy.
- 02
Publish the tool list and boundaries
Share the starter list, what the budget is for, what data is off-limits, and where to ask questions if someone wants to use something else.
- 03
Launch without a mandatory class
Offer examples and optional office hours, but let people start with their own lives. That is where the reps come from.
- 04
Review the signal quarterly
Look for adoption, stories, support needs, and policy confusion. Adjust the budget or guidance without adding bureaucracy.
05 · Reviewer guidance
Frame it differently for each reviewer.
The same pledge has different approval questions. Answer those directly instead of making every reviewer infer the part they care about.
People teams
Position it as a trust-forward learning benefit that reaches the whole person, not a narrow productivity mandate.
Finance
Keep the spend capped per person and review it quarterly. The upside comes from voluntary use, not a large platform commitment.
Security
Separate personal experimentation from company-data workflows. Clear boundaries matter more than pretending people will not experiment.
Ready to turn this into the first internal note?
Use the proposal generator to turn these choices into something a manager, People lead, or finance partner can react to.