AI Workspace

I set your team up with its own AI workspace.

Most AI prototypes look generic. I build a workspace from your code, Figma files and docs. What your team builds there looks like your product.

Fixed price · 6 weeks · Your design system

Get in touchBook a call

What changes for your team

Ideas get clickable in days
Test an idea with users before your team spends a sprint on it.
Everyone can prototype
Designers and product managers build on their own. No waiting for a frontend slot.
The knowledge stays
Rules live as files in your repo. Every session starts with them, also after I’m gone.

€24,999 / fixed

  • – A workspace repo, owned by your company
  • – DESIGN.md and voice.md, written from your design system and brand
  • – Your component library, ready for Claude
  • – Skills and a review agent that check every prototype
  • – Training for your team in weeks 5–6
  • – Done in 6 weeks

Get in touchBook a call

Process

  1. Weeks 1–2AnalysisI go through your frontend code, Figma files and docs, and talk to the people who design and build.Your part: access, and a kickoff with your team.
  2. Weeks 3–4SetupI build the workspace and write the rules for AI. You see the first prototypes built in it.Your part: feedback on the first prototypes.
  3. Weeks 5–6HandoverI train your team. Everyone builds a prototype on their own.Your part: time for training.

Result

A workspace, as a repo, where your team builds prototypes with AI on its own.

Your context: Figma library, Design tokens, Component library, Frontend code, Storybook, Brand guidelines, Tone of voice, Product docs, User research, Roadmap, Domain terms, Team workshops, Sample data, Personas

your-company/ai-workspace

Private
main10 items
Tim HartmannHandover: ready for your team
  • .claudeSkills and a review agent
  • componentsYour component library, ready for AI
  • dataSample data and personas
  • docsProduct, audience, glossary, UI patterns
  • prototypesWhere your team builds
  • stylesYour tokens: color, type, spacing
  • CLAUDE.mdRules and checks for every session
  • DESIGN.mdYour design system, written for AI
  • README.mdHow to start a prototype
  • voice.mdYour tone and wording

Questions

Is this right for us?

It is if you have a product in use, a design system in Figma or in code, and a team that wants to test ideas faster. It isn’t if you’re still looking for your product, or if you need production code.

Does it work with our own component library?

Yes. If your library runs in React, the workspace uses it directly. If it only exists in Figma or in another stack, I rebuild the parts you need with shadcn/ui and your tokens. Either way, prototypes look like your product.

Which tools and licenses do we need?

A Claude plan for everyone who builds prototypes, and Claude Code, which comes with it. Plus access to your Figma files and your frontend repo. Your company buys the plans, so the accounts stay yours.

Where do our code and data go?

The workspace is a repo in your company’s account and belongs to you. Your team works in it with your own Claude plan, under your company’s terms with Anthropic. Sample data is realistic or anonymized, never production data.

Do the prototypes go into production?

No. They’re for testing ideas with users and stakeholders. They use your components and look like your product, but they leave out data access, security and deployment. Your developers still build the real feature.

What happens after the handover?

Your team owns the workspace and keeps it up to date. The rules live next to the code, so updating them is part of normal work. Six weeks give you a solid start, not a finished rulebook. If you want help later, book me by the day. See the day rate →

Why a fixed price?

You know the cost before we start. Scope and timeline are fixed: six weeks, one workspace, training for your team included.

Can you just build the prototypes for us?

Yes. Book me by the day and I join your team. See how that works →

Want this workspace for your team? Get in touch or book a call.