# Start Sign up, then 5 steps. About ten minutes, and nothing to install. The work runs on our servers on the schedule you set; this site holds your connections, shows you what ran, and is where you approve anything that leaves. **These are the product's own steps.** The 5 below are what a new account opens on, in the order it opens on them, and the readiness rail on [Home](https://salesascode.com/home) counts the same 5. New to the model? Read [Concepts, how it runs](https://salesascode.com/docs/concepts#how-it-runs) first. ## Sign up, and pick your roles Two ways in. [/signup](https://salesascode.com/signup) with your work email sends a magic link; click it and you are in, with no password unless you set one later. Or [/login](https://salesascode.com/login) and continue with Google, which skips the email round-trip. We store the Google `sub` claim, so the same Google account resolves to the same Sales as Code account even if you change the address on it later. Either way you land on the first step below rather than on a dashboard with nothing in it. It is one field, your website, and it needs no payment, so you can finish it before deciding anything about a plan (63.B). Then choose at [/pricing](https://salesascode.com/pricing): - **The Founder plan**, $990 a year, carries all 9 roles. This is the shape for someone doing their own selling: the roles feed each other, and Home ranks across all of them. - **A single role**, its own yearly subscription, for someone who does one job rather than all of them. Every role page under [the library](https://salesascode.com/docs/library) lists its price and what it runs. Already own gtmcron's one-time plugins, or an All-Access membership? Everything you bought, you keep, and both remain purchasable. [Licensing & renewal](https://salesascode.com/docs/library/licensing) covers how that sits alongside a subscription. ## Tell your roles about the business Point us at your website. We read it and hand back a draft you edit and confirm, in about a minute. This one is first for a reason. Every role reads your business record before it writes a word, so what you put here decides whether the advice is about your market or about selling in general. Point it at your website, your repo, a Drive folder or an upload, and it hands back a draft you edit and confirm, which is the [GTM Context Dossier](https://salesascode.com/docs/library/gtm-context-dossier). A question you skip stays blank rather than being guessed at. ## Add your AI provider key Paste a key from Claude, OpenAI or OpenRouter. Your agents run on your key, so we never bill you for inference. Every account runs the AI skills on its own key, which is why we never bill you for inference and never meter what you generate. Three providers work today: Claude, OpenAI and OpenRouter. Paste the key once in your console under Settings and it covers every role you hold. The free deterministic checks run without it, so the schedule is not idle while you fetch one, but nothing written or drafted appears until a key is stored. ## Connect a data source Connect your CRM or inbox (or load sample data to try it first). Connections are OAuth in [Settings, Connect](https://salesascode.com/settings/connect). You grant access once; we custody each token encrypted at rest and read it only on your schedule. Tokens are never sold and never used to train. Revoke any of them at any time and the next run reports the source as disconnected rather than failing silently. No CRM yet? Load the sample data and watch a full morning before you connect anything real. ## Choose where output goes Pick a destination: the in-app queue, or Google Drive. Three destinations: the in-app review queue, a Google Drive folder, or a draft in your mailbox. This is where the work lands, not where it goes. A message to a customer still waits in the [dispatch queue](https://salesascode.com/docs/library/campaigns) for your approval. ## Turn the runtime on Flip the runtime on from the Schedule tab so your agents run on a schedule. Until you flip this, nothing runs. After you flip it, each role you hold takes its scheduled pass and reports into [Home](https://salesascode.com/home). Day one is short, and that is correct: one connected source and no history means a short line and several roles reporting that they raised nothing. A role with nothing to say says so rather than filling the space. **Done.** Open [Home](https://salesascode.com/home) for the ranked morning, and [Activity](https://salesascode.com/rollup) for every run with what it produced and what it cost. [How to read Home](https://salesascode.com/docs/library/home) walks the four blocks and the order they are in. ## Common first-day issues - **"A panel says I am not licensed."** Checkout has not granted entitlements yet, or you bought under a different account. Check [/settings](https://salesascode.com/settings); if a purchase completed but is not showing, give the Stripe webhook a minute and reload. - **"A run stopped and said a tool is not connected."** The token expired or was revoked. Reconnect at [/settings/connect](https://salesascode.com/settings/connect) and the next scheduled pass picks it up. - **"Home is empty."** Nothing has finished a run yet. The readiness rail names the step still open; the most common one is the runtime switch. - **"A draft has not gone anywhere."** That is the design. A draft is refused at the send layer until a signed-in person approves that exact draft, and sending is off entirely on a new account. Turn it on in Settings when you are ready; with it off, an approved draft is recorded as held rather than sent, so you can run the whole thing for a month and read what it would have said. --- More for agents: [llms.txt](https://salesascode.com/llms.txt), [full reference](https://salesascode.com/llms-full.txt), [OpenAPI](https://salesascode.com/openapi.json), [sitemap](https://salesascode.com/sitemap.xml).