Every session starts from zero
You re-explain the same project, the same constraints and the same preferences before any work begins.
AI workspace setup
Your AI tools should know how you work.
Raava configures Claude Code, Codex and the workspace around them against your real projects, so you start with useful context, relevant skills and a workflow you can follow.
One-time setup. Clear scope. No lock-in.
If your setup depends on what you remember to prompt, it is not really a system.
The useful instructions are scattered
Good context sits in old chats, half-finished notes and files nobody opens twice.
Too many skills, no reason to pick
Plugins and skills accumulate because they looked useful, not because they serve a job you actually do.
Output is fine, the workflow is not
The model produces good work once, then the next attempt takes a different route and you cannot tell why.
The fix is not adding every tool. It is choosing and configuring the right pieces around the work you actually do.
What changes
| Before | After the setup |
|---|---|
| Re-explaining the same context | Project instructions carry the agreed context |
| Plugins collected at random | Tools chosen for a stated purpose |
| Output that varies run to run | Clear rules, workflow steps and review points |
| Reluctance to change anything | A handover that explains how to use and maintain it |
This is a model of the working setup, not a promise that every answer will be right. Good context makes good output likelier, not certain.
What Raava configures
Six pieces of work, in the order they usually happen.
Requirements and workflow discovery
What you do, what you repeat, and which single workflow is worth setting up first.
Core workspace configuration
Installation, permissions, safety settings and a project structure that holds up.
Project context, instructions and rules
A written record of how your work should be approached, so the agent reads it instead of guessing.
Relevant skills, plugins and connections
A short, chosen set. Each one earns its place against a job you named.
Reusable task flows and checkpoints
The steps you repeat, written down once, with the points where you check the work.
Handover and next steps
A working session plus written instructions, so the setup stays yours to change.
How it works
01
Choose
Pick Essentials or ask about Custom. Payment is handled by Stripe.
02
Tell us about the work
A short structured intake. Share only what the work needs.
03
We configure and test
Raava builds the agreed workspace and checks the primary workflow end to end.
04
You take control
You receive the configured workspace, the written guidance and the included support period.
Typical delivery: 3–7 business days, depending on the requirement.
Two ways in
Choose Essentials for a strong foundation on one clear use case. Choose Custom when the setup has to reflect several projects, a team, or a business workflow.
Essentials
Price unavailable
A personal AI workspace set up properly the first time, around one workflow you actually run.
Best for: One person, one main workflow, and a faster start than a weekend of setup guides.
- Personal requirements discovery
- Claude Code installation and configuration
- Personalised CLAUDE.md and workspace rules
- Up to 5 curated skills, up to 2 plugin/MCP integrations
- 1 custom command or workflow
- 30-minute handover session
- 3 business days post-delivery support
Get in touch and we will invoice you directly.
Custom Setup
Price unavailable
A workspace and working rhythm built around your projects, tools and constraints.
Best for: Work spanning several projects, specialised requirements, a team process, or client work you repeat.
Inclusions are agreed with you during scoping, against the projects and tools the work actually involves.
Get in touch and we will invoice you directly.
Third-party subscriptions, usage charges, custom software development and ongoing support are not included unless stated in your selected package or quote. We will tell you before recommending anything that creates an additional charge.
Side by side
| Feature | Essentials | Custom Setup |
|---|---|---|
| Discovery depth | Personal requirements | Scoped with you |
| Projects configured | 1 | Scoped with you |
| Curated skills | Up to 5 | Scoped with you |
| Plugin / MCP integrations | Up to 2 | Scoped with you |
| Custom commands or workflows | 1 | Scoped with you |
| Project rules and context | Personalised CLAUDE.md | Scoped with you |
| Handover | 30-minute session + quick-start instructions | Scoped with you |
| Post-delivery support | 3 business days | Scoped with you |
Still unsure?
Four questions. Your answers stay in your browser and are not sent anywhere.
0 of 4 answered.
Your workspace stays yours.
- We ask for the minimum access the work requires, and often none at all.
- We prefer accounts you own and credentials scoped to one project.
- Never send passwords, API keys or recovery codes through the intake form. We will share a secure method if access is genuinely needed.
- Temporary access is removed or returned at handover.
- Your content is not used as an example without your permission.
When a workspace setup is not the whole problem
Three signs the work is bigger than one person’s setup.
Questions
It is a configured working environment for an AI coding assistant: the installation, the project instructions it reads, the skills and integrations it can use, and a workflow you can repeat. The setup is the part most people skip.
Claude Code and Codex are the usual starting points, along with the editor, version control and any integrations your work already depends on. We confirm the list against your requirements before starting.
No. Essentials is often bought by people who are comfortable with software but have never configured an agent. The handover session assumes no prior knowledge.
Essentials sets up one person around one main workflow at a fixed price. Custom is scoped with you when the work spans several projects, a team process or specialised requirements, so its figure is a starting point rather than a fixed fee.
No. Third-party subscriptions and usage charges are yours and are billed by those providers directly. We tell you before recommending anything that adds a cost.
Often not. Where access is genuinely required we ask for the least that will do, prefer accounts you own, and return or remove that access at handover. Never send secrets through the intake form.
Yes. An existing workspace is usually easier to work with than a blank one, because it already shows how you work. We tell you what we would keep and what we would change before touching anything.
You are sent to a confirmation page and asked to complete a short intake about the work. We confirm scope, then configure and test the agreed workflow.
Essentials includes a 30-minute handover session and three business days of post-delivery support. Custom support is agreed as part of its scope.
No. Configuring a workspace and building an application are different engagements. If the intake shows you need software built, we say so and scope that separately rather than doing it quietly inside a setup package.
Start with a workspace that is built for the work.
Payment is handled by Stripe. Clear next steps immediately afterwards.