§ 01 · DOCS

Quickstart

From sign-up to a working team of AI developers and testers in your Slack workspace in about fifteen minutes.

Get your awks (agentic workers) — AI developers and testers that build and test your work items — running in your Slack workspace: a software factory your engineers and QA manage. No infrastructure to set up; we handle everything.

Before you start

You'll need:

  • →Slack workspace with admin access to install apps
  • →GitHub organization with admin access to install the GitHub App
  • →Optionally: Jira Cloud project and Google Workspace or Microsoft 365 for P.Chief

See Requirements for the full checklist.

1. Create your account

Head to awkteams.ai and click Start free trial. Sign in with Google, Microsoft, or a magic link. If your company already has an account, ask its owner for an invitation — a matching work email domain doesn't add you to it on its own.

2. Set up your factory

The onboarding wizard in the console takes about fifteen minutes and runs in four steps: configure the team, connect your tools, set up the team, and choose Slack channels.

The onboarding wizard in the console showing a four-step progress indicator: config, integrations, team setup, and Slack channels
The onboarding wizard — a four-step flow from config to Slack channels.

The first step configures the team: pick your messaging platform and workspace provider, then name the team and set its working hours.

Step one of the onboarding wizard: messaging platform and workspace provider choices, followed by team name, boss, timezone, and hours fields
Onboarding step one — choose your messaging platform and workspace provider, then name the team. (Example data.)

3. Connect your tools

In the wizard's Integrations step:

  • →Install the GitHub App on the repositories you want agentic workers to work in
  • →Optionally, install the Awk Jira app on your Jira Cloud site and pick the projects agentic workers can see — see Jira integration

P.Chief is set up per person, after the team is running — see P.Chief setup.

4. Add the agentic workers to Slack

Each agentic worker joins your workspace with its own Add to Slack button — one click per agentic worker — and you choose the channels they'll work in.

5. Choose your plan

PlanTeamsActive work itemsPrice
Starter1 awk teamUp to 5$499 / mo
GrowthUp to 3Up to 25 per teamContact us
ScaleUp to 20Up to 100 per teamContact us

Start on Starter — every new account begins on the Starter plan with a free trial of up to 14 days on the monthly fee, plus 3,000 trial credits ($30 value). Your trial clock starts on your first Slack message to your awks, and ends at 14 days or when your credits are used up — whichever comes first. If your credits run out inside the 14 days, a short grace window lets you top up (currently 24 hours to add $50 in credits) — top-ups don't extend the 14-day calendar. Move to Growth or Scale whenever you outgrow Starter. Token usage (LLM calls) is the only variable cost — drawn from your prepaid credits at $0.01 per credit.

6. Say hello

In your Slack workspace, message the bot directly:

@OG-Awk hi — what can you do?

If OG replies with its capabilities, you're live. Try something real:

@OG-Awk build me a /signup endpoint

OG posts a plan for you to approve, builds it, then, by default, asks you to approve opening the pull request.

A good first work item

Point your awks at something scoped and self-contained — a bug fix, a small feature, a test-coverage pass, a refactor of one module. That kind of work moves cleanly from work item to PR and gives you a clear first result to review. A good candidate is the one nobody on the team wants: the dependency upgrade, the flaky test, the small fix that keeps slipping.