Skip to content →

Product Pricing and Descriptions

The Learning Circle

Tokens Helpdesk is a Learning Circle subscription for 2 to 5 people who want to work on AI side by side. Friends who work together. Colleagues in a small business. A family running a family business. Members who trust each other enough to try something new together.

New to Tokens Helpdesk? Read the welcome page for the Circle mechanic and origin story before pricing details.

Pricing

Monthly: $20 per person per month or

Annual: $200 per person per year.

What’s included in every plan:

  • Monthly Circle progress PDF, delivered on the 5th of the following month
  • Up to 5 Circle members
  • Monthly Circle Challenge, delivered on the 1st of each month
  • Tuesday and Thursday Circle texts throughout the month, supporting the current Challenge
  • Daily habit messaging for every Circle member, 7 days a week
  • 2 Circle questions per month, banked up to 24, with 24-hour AI plus human review on every question

How the Circle works

  1. One person starts the Circle. Sign up, pay for your own seat, and pick your Circle name (can be changed). You are the Host, which means you invite the others with a link we provide. The subscription belongs to the Circle, not to you personally.
  2. Invite 1 to 4 others. Send your link to friends or colleagues. Circles are 2 to 5 people. When everyone consents to receive messages, they join the Circle.
  3. The Circle receives its first Challenge on the 1st of the month. A downloadable brief that names the deliverable your Circle will produce together over the month. The Challenge sets the context and the destination.
  4. Tuesday and Thursday texts throughout the month support the Challenge. Each text is a clue, a validator, or a recommended approach that ties back to the Challenge. Everyone in the Circle receives the texts on the same day.
  5. Daily habit messages run alongside. Each Circle member receives a daily message tuned to their subscriber type · Navigate, Build, Scale, or Mix. Set at sign-up, changeable any time.
  6. Ask questions when you need to. Any Circle member can message QUESTION to the Helpdesk. The Circle decides who receives the reviewed answer within 24 hours. Unused questions roll forward, up to 24 banked. Every question and answer is stored in the Circle’s monthly PDF.
  7. The Circle completes the Challenge together at month’s end. In person if you can, on a call if you cannot. The 2 monthly Helpdesk questions are typically saved for the last week when the Challenge is taking shape.
  8. The monthly PDF arrives on the 5th of the following month. Everything your Circle built, plus the next Challenge.

The monthly Circle Challenge

The Challenge is the container. Everything else is designed to support it.

Circle Challenges are hands-on deliverables the Circle produces together. For example ·

  • A dashboard the Circle builds together
  • A workflow that automates a repetitive task each member has in common
  • A customer-facing tool
  • An internal automation
  • A small process improvement each Circle member takes back to their own work

Every Challenge is broken into small pieces before it goes out to Circles. Those pieces become the Tuesday and Thursday texts, so each text either validates something the Circle is trying, drops a clue the Circle needs, or recommends an approach the Circle can test.

Every Circle we have watched work well has one thing in common · the members already meet up sometimes. If your Circle is 2 to 5 people who can be in the same room once a month, you are going to get a lot out of this. If your Circle is scattered, the Tuesday and Thursday texts still land, the questions still land, and the Challenge completion becomes a scheduled video call.

The monthly Circle progress PDF

Delivered on the 5th of the following month. Shows ·

  • What your Circle built (the Challenge deliverable)
  • Which Tuesday and Thursday texts drove the build
  • What the Circle figured out along the way

Consider it a report-out you can share with your Challenge product.

Choose your subscriber type

Each Circle member selects their subscriber type at sign-up · Navigate, Build, Scale, or Mix. People come to AI from different starting points, and content is tuned to that voice, vocabulary, and workflow context.

1. Onboard

The Onboard subscriber has yet to choose AI as a work practice. They have encountered AI through provided surfaces (search overviews, autocomplete, spellcheck suggestions) and have watched colleagues use it, but they have yet to pick their own tool, open their own account, or decide when AI is worth their time.

Common roles:

  • Frontline and service. Retail associate, food service worker, hospitality staff, transportation worker, home services provider, caregiver, security officer.
  • Skilled trades. Electrician, plumber, carpenter, HVAC technician, welder, mechanic, machinist, landscaper.
  • Administrative and clerical. Office administrator, front desk coordinator, records clerk, scheduler, executive assistant, receptionist.
  • Public sector and community. Local government staff, library assistant, school support staff, community health worker, faith community staff, parks and recreation staff.
  • Health, education, and human services. Direct care worker, teacher’s aide, paraprofessional, medical assistant, dental assistant, social service caseworker.
  • Returning workers and career changers. Someone re-entering the workforce, changing sectors, or moving into a first knowledge-work role after years in another field.

What unifies Onboard subscribers is the mix of a working adult’s judgment with an early relationship to AI. They know their job. They have not yet decided whether AI belongs in it. They want to make a fair call before adopting a tool that other people are already using, and they want the call to be their own.

Their expertise is in their trade, their sector, and the tacit knowledge that a workday builds up. AI is one more system they can choose to add. They want the coaching to respect that they are capable adults making a considered choice, and to keep the vocabulary plain while it does.

AI can shorten a task, help draft a message, translate a passage, or answer a small question. The Onboard subscriber brings the working context and the judgment about whether the answer fits their situation. The coaching brings a clear picture of what the current tools are, what they are for, and one small thing to try today. Together, the pair moves the subscriber from watching to using at the pace they choose.

Onboard coaching examples:

  • What ChatGPT, Claude, Gemini, and Perplexity are, in plain language.
  • Small tasks to practice.
  • How to read an AI answer critically. What to trust. What to check.
  • Free versus paid. When free is enough. When paid earns its cost.
  • The difference between an AI answer and a search result, and when each is the better move.

Onboard security and cybersecurity examples:

  • What to share with an AI tool and what to keep out. Names, addresses, health information, financial details, employer information.
  • How to recognize AI-generated scams in email, SMS, and voice calls.
  • Account basics. Strong passwords, multifactor authentication, and how to spot a fake sign-in page.
  • What happens to the words you type into a free AI tool. Where they go. Who might see them.
  • How to close, delete, or pause an account when the subscriber decides a tool is no longer for them.

2. Navigate

The Navigate subscriber is central to how their organization runs. They carry the volume, the customer contact, and the operational judgment that keeps things working.

Common roles:

  • Human resources. HR lead, HR coordinator, HR business partner, benefits specialist, recruiter, learning and development lead, employee relations specialist.
  • Marketing. Marketing coordinator, marketing manager, content lead, brand specialist, digital marketing lead, marketing operations, community manager.
  • Operations. Operations manager, operations coordinator, business operations lead, chief of staff, program manager, project coordinator.
  • Customer experience. Customer success lead, customer service manager, member services lead, patient services coordinator, client relations manager.
  • Program and specialist roles. Admissions or grants coordinator, compliance specialist, contract administrator, event manager, communications specialist.
  • Mid management. Department heads, department leads, team leads across the categories above.

What unifies Navigate subscribers is they own outcomes. They talk to customers, members, patients, or clients more than most people in the organization. They make sure the organization functions well.

Their expertise is in operations, people, communications, and the systems of work that keep an organization running. AI is now one of the systems of work they manage.

AI can amplify their capacity or waste their time, and they know it. They want a working mental model of the AI ecosystem so they can make good calls about tools, workflows, and where to invest their attention. They want coaching that respects their responsibility and their expertise. The Navigate subscriber brings the operational judgment, the customer context, and the domain expertise. AI brings capacity, options, and pattern recognition from other contexts. Together, the pair makes something better than either might alone.

Navigate coaching examples:

  • Current, relevant ways to use AI specific to their work and sector.
  • A working mental model of the AI ecosystem. Models, workflows, and what fits where.
  • Cost and ROI coaching.

Navigate Security and cybersecurity examples:

  • Recognizing AI-enabled phishing patterns in email, SMS, and voice.
  • Basic KYC and AML awareness for functions where it applies. HR onboarding, member intake, marketing list building, customer intake.
  • Vendor security signals to look for when the team considers adopting a new AI tool.
  • Recognizing when a request warrants escalation to IT or security, and how to raise it well.
  • Password managers, multifactor authentication, session hygiene.

3. Build

The Build subscriber runs something end to end. A whole business. A whole function. A whole practice. They own the P&L, the customer relationship, or the outcome directly. When something goes wrong in their domain, it lands on them.

Common roles:

  • Owner-operator. Small business founder. Solopreneur. Managing partner. Studio owner. Shop owner. Independent practice owner (consultant, coach, accountant, lawyer, agent, therapist, designer, developer, tradesperson).
  • Function head. Head of sales at a small or mid-size company. Head of marketing. Head of operations. Head of customer success. Head of finance. Chief of staff.
  • Executive director. Executive director of a nonprofit. Director of a small foundation. Head of a small association.
  • Multi-hat senior operator. Managing director of a small firm. Chief operating officer at a company under fifty people. General manager of a location or region.
  • Independent professional running a practice. Solo attorney. Solo accountant. Solo agent. Solo therapist. Solo designer. Solo consultant. Franchise owner.

What unifies Build subscribers is owning outcomes across multiple domains at once. Sales, marketing, operations, HR, tax, legal, and customer are not separate departments in their world. The subscriber uses AI daily. They have preferred tools. What they want is coaching that supports them to use AI across the many domains they own, and see the business ROI clearly.

The Build subscriber thinks about: Did I quote that project right? What am I missing on the tax question? Is my sales copy good? What am I supposed to know about GDPR? Should I be running ads? AI serves as the working partner who supports closing those loops in a short time instead of spending three days reading the documentation.

AI is a working partner. A team member who covers the domain the Build subscriber cannot cover alone. The Build subscriber brings the business judgment, the customer context, and the operational instinct. The coaching brings the specific angle and the pattern that would take hours to work out from scratch.

Builder example priorities:

  • Cover the weak spots without hiring four people they cannot yet afford.
  • Expand the operation with AI as added capacity.
  • Compete with bigger competitors by punching above weight class.
  • Compound the ROI over weeks and quarters.
  • Know their business AI spend is paying off.

Builder security and cybersecurity example topics:

  • Vendor risk when adopting AI tools. What to check before signing up. Data handling terms. Where the data is stored. Subprocessor lists. Model training on customer inputs.
  • Contract confidentiality. AI review of NDAs and contracts without leaking counterparty information.
  • Cyber insurance implications of AI adoption. What to disclose. What to document.
  • Recognizing AI-enabled phishing and business email compromise patterns aimed at owner-operators.
  • Backup and recovery hygiene when business workflows depend on AI outputs.

4. Scale

The Scale subscriber has AI at the center of what they are shipping. They own architectural decisions, deployment decisions, or outcome decisions that other people depend on. Real stakes. Real numbers. Real product or service.

Common roles:

  • AI product founder. Building an AI-first product. Owner of the model routing, the agent design, the cost curve.
  • Senior operator running an AI initiative. Inside a larger company, responsible for the AI adoption, integration, or transformation program with a measurable target and a budget.
  • Consultant or agency principal selling AI services. Building bespoke AI workflows or systems for clients. Responsible for delivery and margin.
  • Technical practitioner deploying AI systems at scale. Engineering leader, staff engineer, principal engineer, ML engineer, applied AI engineer. Shipping production AI.
  • Product or engineering leader responsible for AI features. Head of product with AI in the roadmap. Head of engineering with AI in the stack.
  • Sector expert applying AI to a measurable outcome. Deep sector expertise (medical, legal, financial, scientific, industrial) paired with a specific AI-applied business or research outcome.

What unifies Scale subscribers is building, shipping, or deploying with real stakes. They are responsible for what an AI system does or does not do in production or in the client’s hands.

The Scale subscriber has technical depth or sector depth, or both. Scale is for engineers and for deep sector experts alike. A pharma expert applying AI to clinical operations, a financial services operator applying AI to compliance workflows, a legal services principal applying AI to matter management, all belong here alongside the AI engineer.

Scale coaching examples:

  • Model behavior. Claude, GPT, Gemini, Grok, open-weight models. Strengths, weaknesses, and specific behaviors under production load. Model routing. When to use a small model, a large model, a reasoning model, or a specialized model.
  • Prompt caching. When it applies. How much it saves. What breaks it. Model routing for cost. When a smaller model with a fallback saves more than the flagship. The buy vs build calculation at production scale. Protocols. MCP, tool use, structured output, function calling, streaming protocols. What is landing in production. What is not.
  • Deployment patterns. Latency budgets. Streaming. Batching. Fallback and retry logic. Caching layers.
  • Evaluation frameworks. How to know your AI system is working. What to measure. What to log. Systems supervision. Monitoring, alerting, and incident response for AI systems.
  • Batching and asynchrony. When to batch. When to stream. When to defer. Cost anomaly detection. What to log so a bad prompt does not bankrupt the run.

Scale security and cybersecurity example topics:

  • Architectural security. Prompt injection defenses. Agent trust boundaries. Least-privilege tool design. Backup and recovery hygiene when business workflows depend on AI outputs.
  • Deployment security. Secrets handling in agent systems. Audit logging for AI actions. Rate limiting and abuse detection.
  • Model provider risk. Data handling terms. Region availability. Provider redundancy. Model deprecation risk. Agent supervision. When to require human confirmation. When to allow autonomous action. How to design the trust ladder.
  • Vendor risk when adopting AI tools. What to check before signing up. Data handling terms. Where the data is stored. Subprocessor lists. Model training on customer inputs.
  • Cyber insurance implications of AI adoption. What to disclose. What to document.

5. Mix

A Mix of all four subscriber types.

Circle members can change subscriber types any time. This is a checkbox, not a ladder.

The 14-day free trial

Two weeks is enough time to feel the Circle rhythm. No credit card required to start.

At day 8 of the trial, the Circle Host receives an opt-in link if the Circle wants to continue. If the fit is wrong, the trial ends on day 14, and there is nothing to cancel.

We won’t ask you to pick a subscriber type on day one. During your 14-day trial, each message arrives labeled Navigate, Build, or Scale, so your best-fit track reveals itself through use. When you subscribe at the end of your trial, we’ll show you plan details side by side for you to select your initial track. You can change tracks anytime.

When the Learning Circle fits

  • You have 2 to 5 people who already talk to each other and want to work on AI together
  • You like a rhythm of daily habit messages plus twice-a-week collaboration
  • You like a monthly reason to meet up IRL (or on a synchronous video call)
  • You like a monthly progress record of what your Circle built
  • You like a small human-reviewed question channel your Circle can share

When the Learning Circle does not fit

  • You want individual AI coaching without a group · see CutTokenCosts.com
  • You need company-wide reporting and finance-leader briefs · see ReduceTokenCosts.com
  • Your group is 6 or more people · run two Circles side by side, or contact us at Connect@TokensHelpdesk.com

Ready to start a Circle?

Sign Up Link

We won’t ask you to pick a subscriber type on day one. During your 14-day trial, each message arrives labeled Navigate, Build, or Scale, so your best-fit track reveals itself through use. When you subscribe at the end of your trial, we’ll show you plan details side by side for you to select your initial track. You can change tracks anytime.

Related pages

If you want a solo subscription for individual AI habit coaching, see CutTokenCosts.com.

If you are a CFO or CEO looking at next quarter’s line-item review, ReduceTokenCosts.com offers additional personalization and reporting options.

For the underlying data (pricing volatility, benchmark studies, and the dashboards we’re building around cost per finished output), start at TokenCosts.ai.Contact · Connect@TokensHelpdesk.com. Message HELP anytime · a human replies within 24 hours. A product of 2 Degree Shift, a California C Corporation.