Your first hour

#1. Connect your cloud account

Everything below is optional and nothing expires. But this is the order that gets you to useful fastest, and each step makes the next one better.

Do this first. It is what moves your workspace onto infrastructure you own, and doing it before you enter data means nothing has to be moved later.

It is one consent screen against your own account, and it is where you choose your data region. If data residency is something you have to prove to someone, choose the EU — it carries a jurisdiction guarantee enforced at the infrastructure level rather than by us as a setting.

See Bring Your Own Cloud.

#2. Set your brand

Two modules, ten minutes, and everything downstream improves.

Brand assets holds your logos, colours, images and brand files in one place. Tone of voice is where you describe how your brand writes — the vocabulary you use, the things you never say, whether you are warm or exact.

Do this early because every AI-drafted newsletter, social post and generated image reads from it. Fill it in later and you spend the intervening weeks correcting drafts that sound like nobody in particular.

#3. Bring in your clients

Import your contacts and companies, or add a handful by hand to feel how it works. The CRM is the spine — a client here is the same client in Projects, Billing and Documents, and linking them later is more work than starting linked.

#4. Create one real project

Not a test project. A real one, with its actual client attached.

This is where the connections become visible: the project knows its client, time logged against it becomes invoice lines, its documents carry its context, and its milestones show up on the calendar. One real project teaches you more than an hour of clicking around.

#5. Connect your AI

Generate a personal access token and point Claude Code, Cursor, Claude Desktop or claude.ai at your workspace. From then on your AI works your real data instead of guessing at it.

See Connect your AI.

#6. Invite your team

Invite one person first and look at what they see. Roles are starting points you can reshape, and the fastest way to understand the permission model is to watch one colleague land in it.

#What to leave for later

Deliberately not in your first hour:

• Design system, wireframes and components. These pay off when you have a project that needs them, not before.
• Automations and reminders. Learn your own rhythm first, then automate the parts that repeat.
• Everything in the module catalogue. Turning on twelve modules on day one produces a sidebar you cannot read. Add them when a real piece of work asks for them.