harnsy

AI agent teams for your field

Pick your field and see the whole team: who does what, how work passes between them, and what comes back to you to check.

Three of these are real runs; the rest are illustrations, not customers.

How every team here works

  1. You say what you need. Tell the lead the goal in your own words.
  2. The lead splits it and picks who does it. Or it hands the task to a role that splits it further.
  3. Roles hand work to each other. They message each other, and the work moves on.
  4. The one who asked checks it. If it is not right, it goes back with a note.
  5. You accept the result or send it back. The lead checks the specialists’ parts; your request waits for your Accept.
How tasks work

Water-supply design

Real run

This is you if… you design water supply for buildings and sign every drawing yourself.

The task

“I’m an independent plumbing and water-supply design engineer. New job: cold and hot water for a three-storey block of 12 flats. I need a draft design package. I check and sign everything myself.”

Engineer played by our team; the agents and their work are real.

How the work flows

  1. You →lead: the job, the pipe material, the pressure and the file formats you want. The lead asks a few more questions with buttons.
  2. Team →you: it says it cannot quote values from a standard it does not have; you choose to have it check sums only.
  3. Data analyst →lead: the table of design flows, from web sources marked as such, for you to check against your own copy when you sign.
  4. Fact checker ✓checks every sum in the table.
  5. Hydraulic engineer →lead: pipe sizes and the riser diagram. You send pipe sizing back with one change, and the team reworks it.
  6. Plain-language writer →lead: the design note.
  7. Lead →you: the result waits for your Accept.
Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

SaaS MVP

Real run

This is you if… you are a solo developer or a small team and want something to show your first users.

The task

“I’m a solo developer. I want an MVP I can show my first users: a landing page with a waitlist, a changelog page and a widget that embeds with one script tag. Hire who you need.”

Founder played by our team; the agents and their work are real.

How the work flows

  1. You →lead: the idea in your own words. The lead asks a few questions with buttons.
  2. Lead →UI designer: the look of the landing page, the changelog page and the widget.
  3. UI designer →MVP engineer: the design; the engineer builds the pages and the widget.
  4. QA engineer ✓checks the page and the waitlist and sends two findings to the engineer, who fixes them.
  5. You →team: the widget back with one change; the team reworks it.
  6. Lead →you: the result waits for your Accept.
  7. A second project’s lead →blog writer, email marketing specialist: for the launch, a launch post and a waitlist e-mail.
Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

A web service in two days

Real run

This is you if… you have an idea for a web service and want a team to build it while you steer.

The task

One conversation became a working service. The founder set the direction, gave feedback and picked the designs. AI teams did the work.

Two days was this project’s timeline, not a promise for every project.

How the work flows

  1. Founder →lead: the idea, in one conversation.
  2. Teams →site and servers: the HR site is built and its servers and DNS set up.
  3. Teams →repository: a GitHub repository of employee bundles, synced with the site and connected to the harnsy app.
  4. Testers ✓run test environments in Docker and test creating organizations, projects and hiring.
  5. Founder →teams: feedback, and a pick between designs.
  6. Teams →founder: the demo is recorded and the service waits for the founder’s Accept.

Needs Claude Code or Codex, signed in (their plans are paid separately)

Contracts

Example

This is you if… contracts reach you before they reach your lawyer.

The task

“A supplier sent a 14-page contract. Tell me what to worry about before my lawyer reads it.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: the contract and what worries you.
  2. Lead →contract reviewer: read the 14 pages and mark the clauses that need attention.
Show the whole flow and what comes back
  1. Contract reviewer →privacy specialist: the clauses about personal data, for a second look.
  2. Contract reviewer ✓checks the specialist’s notes against the contract text.
  3. Plain-language writer →lead: a one-page summary in plain words.
  4. Lead →you: the clauses, the questions and the summary wait for your review. Your lawyer decides.

What comes back for your review

  • The clauses that need attention, each with why
  • Questions for your lawyer
  • A one-page summary in plain words

Not legal advice: your lawyer decides.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Content marketing

Example

This is you if… you publish regularly and a plan, drafts and channels pile up.

The task

“I run a small coffee roastery. Plan a month of posts and articles, and write the first ones.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: your business, your channels and what you want to say this month.
  2. Lead →marketing strategist: a content plan for the month.
Show the whole flow and what comes back
  1. SEO content strategist →marketing strategist: topics people search for.
  2. Marketing strategist →copywriter: the plan and the topics; the copywriter drafts four articles.
  3. Social media manager →posts for each channel from the drafts; the marketing strategist ✓ checks them against the plan.
  4. Lead →you: the plan and the drafts wait for your approval. Nothing is published before it.

What comes back for your review

  • A content plan for the month
  • Four article drafts
  • Posts for each channel
  • A list of topics people search for

Nothing is published until you approve it.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Bookkeeping

Example

This is you if… receipts and statements pile up and you want to see where the money goes.

The task

“Here are three months of bank statements and receipts. Sort the expenses and show me where the money goes.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: three months of bank statements and receipts.
  2. Lead →bookkeeper: sort the expenses by category.
Show the whole flow and what comes back
  1. Bookkeeper →financial analyst: the sorted table; the analyst builds a monthly summary with a chart.
  2. Fact checker ✓adds up the totals again and marks the items that need a receipt or a question.
  3. Bookkeeper →lead: the questions for your accountant.
  4. Lead →you: the results wait for your review. You and your accountant check the numbers; your accountant files the returns.

What comes back for your review

  • Expenses sorted by category
  • A monthly summary with a chart
  • Items that need a receipt or a question
  • Questions for your accountant

You and your accountant check the numbers; your accountant files the returns.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Online store

Example

This is you if… your online shop sells slowly and you do not know why.

The task

“My handmade-candle shop on Shopify sells poorly. Find out why and fix what you can.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: your shop and what sells badly.
  2. Lead →conversion optimization specialist: find what may stop buyers, ranked.
Show the whole flow and what comes back
  1. Conversion optimization specialist →copywriter: the weak product cards; the copywriter rewrites them.
  2. Conversion optimization specialist →Shopify developer: the page fixes; the developer makes them on a separate branch.
  3. Marketplace manager →lead: which fixes the marketplaces where you sell also need.
  4. Lead →you: the list, the cards and the branch wait for you to accept them.

What comes back for your review

  • A list of what may stop buyers, ranked
  • Rewritten product cards
  • Fixes to the shop’s pages, on a branch for you to accept
Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Market research

Example

This is you if… you need to know who already sells what you plan to build.

The task

“Before I build it: who already sells online booking for small yoga studios, and what do they charge?”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: the question and the market you have in mind.
  2. Lead →competitive analyst: a table of who sells what, with sources.
Show the whole flow and what comes back
  1. Prior-art researcher →competitive analyst: similar products the table missed, with dates.
  2. Fact checker ✓marks each claim as checked or not.
  3. Competitive analyst →lead: the gaps few cover.
  4. Lead →you: the table and the gaps wait for your review.

What comes back for your review

  • A comparison table of offers with sources
  • Gaps few cover
  • Claims marked as checked or not
Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Customer support

Example

This is you if… you answer the same customer questions every week.

The task

“We answer the same 30 questions every week. Write the help centre and draft replies for the rest.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: the questions customers repeat, and how you like to sound.
  2. Lead →knowledge base writer: help-centre articles for the repeated questions.
Show the whole flow and what comes back
  1. Lead →customer support agent: reply drafts for new tickets, using the articles.
  2. Support quality reviewer ✓checks tone and rules and sends two drafts back.
  3. Customer support agent →lead: a weekly note on what customers ask most.
  4. Lead →you: replies go out after a person reads them.

What comes back for your review

  • Help-centre articles
  • Reply drafts for new tickets
  • A weekly note on what customers ask most

Replies go out after a person reads them.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Explainer video

Example

This is you if… you need a short video that explains your product.

The task

“A 60-second video that explains our app, with a voice-over and captions.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: what the app does and who it is for.
  2. Lead →copywriter: the script.
Show the whole flow and what comes back
  1. Video director →motion video maker: a storyboard from the script.
  2. Motion video maker →video director: the rendered video with captions.
  3. Video director ✓checks the video against the script and lists the fonts, music and voice used, with their licences.
  4. Lead →you: the video waits for your Accept. The voice is generated, and the hand-over says so.

What comes back for your review

  • The script
  • A storyboard
  • The rendered video with captions
  • A list of fonts, music and voice used, with their licences

The voice is generated, and the hand-over says so.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Hiring

Example

This is you if… you are hiring your first people and want the materials prepared.

The task

“I need my first sales manager. Help me write the job post and plan structured interviews.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: the role you need to fill.
  2. Lead →recruiter: the job post.
Show the whole flow and what comes back
  1. Recruiter →interview designer: the job post; the designer plans structured interviews with questions.
  2. Interview designer →lead: a scorecard template for you to fill in after each interview.
  3. HR generalist ✓checks that the post, the questions and the template fit together.
  4. Lead →you: the materials wait for your review. You talk to the candidates and you decide.

What comes back for your review

  • The job post
  • An interview plan with questions
  • A scorecard template to fill in after each interview

The team prepares the materials. You talk to the candidates and you decide.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Online course

Example

This is you if… you know a craft and want to teach it online.

The task

“Turn my ceramics workshop into a six-lesson online course.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: your craft, who should learn it and what they should be able to do.
  2. Lead →learning designer: the course outline.
Show the whole flow and what comes back
  1. Learning designer →editor and proofreader: six lesson scripts, edited for clarity.
  2. Learning designer →presentation designer: the slides for each lesson.
  3. Learning designer ✓checks each quiz against its lesson.
  4. Lead →you: the outline, the scripts, the slides and the quizzes wait for your review.

What comes back for your review

  • A course outline
  • Six lesson scripts
  • Slides
  • A short quiz for each lesson
Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Real estate listings

Example

This is you if… you list properties and write the same kind of ad again and again.

The task

“I list flats for rent in two languages. Write the listings and compare prices nearby.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: your flats and the two languages you list in.
  2. Lead →copywriter: the listing texts.
Show the whole flow and what comes back
  1. Copywriter →translator: the texts for the second language.
  2. Copywriter ✓checks that both versions say the same.
  3. Lead →data analyst: a table of nearby asking prices, with sources.
  4. Lead →you: the listings and the table wait for your review. A person checks every listing before it is published.

What comes back for your review

  • Listing texts in both languages
  • A table of nearby asking prices with sources
  • Questions to ask the owner

A person checks every listing before it is published.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Data analysis

Example

This is you if… you answer questions with data and the road from a question to a chart is long.

The task

“Our signups fell last week and I don’t know why. Here is the events export: find where and why.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: the question and the export.
  2. Lead →data analyst: the analyst splits it: the funnel by source, by device and by release date.
Show the whole flow and what comes back
  1. Data analyst →data engineer: a clean events table; the engineer sends it back with a description.
  2. Data analyst →BI dashboard developer: the numbers; the developer builds three charts.
  3. Fact checker ✓runs the queries again, finds one wrong date filter, and the analyst fixes it.
  4. Lead →you: the findings and the charts wait for your review. You decide what to do with them.

What comes back for your review

  • The funnel by source and by device
  • Three charts
  • The queries behind every number
  • A list of what to check next

You decide what to do with the findings.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Grant application

Example

This is you if… you apply for grants or public funding and every call wants a different structure.

The task

“Our small studio wants to apply for a regional grant for digital projects. Here are the call and my notes about the project. Draft the application. I check and submit everything myself.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: the call and your notes about the project.
  2. Lead →business analyst: the requirements of the call, as a checklist.
Show the whole flow and what comes back
  1. Business analyst →proposal and RFP writer: the checklist; the writer drafts the application section by section.
  2. Proposal and RFP writer →financial analyst: the budget lines; the analyst builds the table with its assumptions written out.
  3. Editor and proofreader ✓checks the draft against the checklist and marks what is still open.
  4. Lead →you: the checklist, the draft, the budget and the open questions wait for your review. You check every figure and claim, sign and submit.

What comes back for your review

  • The call’s requirements as a checklist, each marked met or open
  • The application draft, section by section
  • A budget table with its assumptions written out
  • Questions only you can answer

The team drafts; you check every figure and claim, sign and submit. Some calls have rules on AI-written text: check yours.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Translation and localization

Example

This is you if… you ship a product in more than one language and the texts drift apart.

The task

“My app’s texts are in English. I need the interface strings and the store page in Spanish and Japanese, in the same tone.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: the strings file, the two languages and the tone of the app.
  2. Lead →localization manager: a glossary of the app’s terms and a list of strings that need context.
Show the whole flow and what comes back
  1. Localization manager →translator: the glossary and the strings; the translator translates both languages.
  2. Translator →editor and proofreader: the translated strings and the store page.
  3. Editor and proofreader ✓checks the texts against the glossary and marks where the two languages say different things.
  4. Lead →you: the strings, the store page, the glossary and the open questions wait for your review. A person who speaks each language reads the texts before release.

What comes back for your review

  • The interface strings in both languages, in your file format
  • The store page in both languages
  • A glossary of the app’s terms
  • Strings that need context or a decision

A person who speaks each language reads the texts before release.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

E-mail newsletter

Example

This is you if… you want to write to your customers regularly and every issue starts from a blank page.

The task

“I run a small online bakery. Set up a monthly newsletter: a template, the first issue and a welcome e-mail for new subscribers.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: your shop, your customers and what you want to tell them.
  2. Lead →email marketing specialist: the structure of an issue and the welcome e-mail.
Show the whole flow and what comes back
  1. Email marketing specialist →copywriter: the structure; the copywriter writes the first issue.
  2. Editor and proofreader ✓checks the texts and the links, and that the issue has an unsubscribe line.
  3. Email marketing specialist →lead: a plan for the next three issues.
  4. Lead →you: the template, the issue, the welcome e-mail and the plan wait for your approval. Nothing is sent before it.

What comes back for your review

  • An issue template
  • The first issue
  • The welcome e-mail
  • A plan for the next three issues

Nothing is sent until you approve it. Whom you write to, and your right to write to them, are yours.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Mobile app prototype

Example

This is you if… you have an app idea and want to see it in people’s hands before you build it.

The task

“I have an idea for a habit-tracking app. Make a clickable prototype I can show to a few people before I build anything.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: the idea and who it is for.
  2. Lead →UX researcher: the people it is for, what they need and the main flows.
Show the whole flow and what comes back
  1. UX researcher →prototype designer: the flows; the designer builds a clickable prototype.
  2. Prototype designer →UI designer: the screens; the UI designer sets the look.
  3. UX auditor ✓walks through the prototype and lists the usability problems.
  4. Lead →you: the prototype, the flows and the questions for your test users wait for your review. You try it with real people.

What comes back for your review

  • The main user flows
  • A clickable prototype
  • Usability problems found in it, ranked
  • Questions to ask your test users

A prototype is not the app: you test it with real people before you build.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Security review

Example

This is you if… you ship software and want a second look at its security before users see it.

The task

“Before we launch, check our Python web app for security problems and risky dependencies. Here is the repository.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: the repository and what the app handles.
  2. Lead →application security reviewer: the code, for common weaknesses.
Show the whole flow and what comes back
  1. Lead →dependency gatekeeper: the list of dependencies, for outdated and risky ones.
  2. Reviewer ✓checks each finding against the code and drops the ones that do not hold.
  3. Application security reviewer →lead: the findings ranked by risk, each with the file and the reason, and the fixes on a branch.
  4. Lead →you: the findings, the dependency list and what was not checked wait for your review. Your engineers decide what to fix.

What comes back for your review

  • Findings ranked by risk, each with the file and the reason
  • Dependencies that are outdated or risky
  • Suggested fixes, on a branch for you to accept
  • What was not checked

A review is not a certificate: your engineers decide what to fix.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Event planning

Example

This is you if… you organise events and the checklist, the budget and the invitations are all on you.

The task

“I’m organising a one-day workshop for 40 people in my town. Plan the programme, the budget and the invitations.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: the idea, the town, the group and what you can spend.
  2. Lead →project manager: the programme and a checklist of what to book.
Show the whole flow and what comes back
  1. Project manager →estimator: the items on the checklist; the estimator gives a budget range with its assumptions.
  2. Project manager ✓checks that every item on the checklist has a line in the budget.
  3. Executive assistant →lead: questions for each supplier, for you to send.
  4. Copywriter →lead: the invitation and a reminder.
  5. Lead →you: the programme, the budget, the questions and the invitations wait for your review. You book, pay and send.

What comes back for your review

  • A programme by session
  • A budget range with its assumptions
  • A checklist of what to book, with questions for each supplier
  • The invitation and a reminder

The team plans; you book, pay and send the invitations.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Pitch deck

Example

This is you if… you are preparing to talk to investors and want to hear the hard questions first.

The task

“I’m preparing to talk to investors. Turn my notes into a pitch deck and tell me where the story is weak.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: your notes, the product and what you plan to ask for.
  2. Lead →startup finance analyst: a table of the figures from your numbers, with the assumptions written out.
Show the whole flow and what comes back
  1. Lead →copywriter: the story of the deck, slide by slide.
  2. Copywriter →presentation designer: the texts; the designer builds the slides.
  3. Pitch critic ✓reads the deck as an investor would and lists the weak points and the questions to expect.
  4. Lead →you: the deck, the figures and the weak points wait for your review. Every figure and claim is yours to check.

What comes back for your review

  • The story of the deck, slide by slide
  • The slides
  • A table of the figures with their sources and assumptions
  • Weak points and the questions investors may ask

Every figure and claim is yours: you check them before you show the deck to anyone. This is not investment or financial advice.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Cloud bill review

Example

This is you if… your cloud bill grows and nobody can say which service is behind it.

The task

“Our cloud bill keeps growing and nobody knows why. Here is last month’s invoice export: find where the money goes and what we could cut.”

An illustration of the kind of work, not a real run or a promise of results.

How the work flows

  1. You →lead: the invoice export and what each project does.
  2. Lead →cloud bill reader: the bill split by service and by project.
Show the whole flow and what comes back
  1. Cloud bill reader →financial analyst: the split; the analyst finds the items that grew.
  2. Financial analyst →cloud architect: the items that grew; the architect proposes savings, each with the risk of the change.
  3. Fact checker ✓recalculates the totals against the export.
  4. Lead →you: the split, the items that grew and the possible savings wait for your review. Your engineers decide and make every change.

What comes back for your review

  • The bill split by service and by project
  • The items that grew
  • Possible savings, each with the risk of the change
  • Questions only your team can answer

This team works from the export only: your engineers decide and make every change in your cloud.

Start free

Needs Claude Code or Codex, signed in (their plans are paid separately)

Your field is not here?

Describe the job in your own words. The lead picks specialists from hr.harnsy.dev and tells you; you can let anyone go. Where the catalog has nobody, you describe the specialist yourself.

Needs Claude Code or Codex, signed in (their plans are paid separately)

How a team grows

Nothing here happens by itself. The lead adds a role when the work needs one, and you can see what changed.

  • The lead adds roles. When the work needs one, the lead adds a role and opens an agent that takes the seat. harnsy adds no role on its own.

  • A full context means a handover. When an agent’s context fills up, it writes a handover note and the lead opens a successor on the same seat.

  • Instructions have versions. Role instructions and team documents are versioned. The lead edits them and can roll back; only the lead or you change them.

Your agents are waiting on you in every project. You're not at your desk.

harnsy Max runs as many projects as you need and brings their questions to your phone: a push notification, or buttons in your project's Telegram or Discord chat.

  1. Answer from your phone.

    A notification about each question or permission request reaches your phone, even when the app is closed. Or answer with a button in Telegram or Discord.

  2. More projects at once.

    Free harnsy runs 2 projects. harnsy Max runs as many as you need.

  3. See the limit before you hit it.

    More projects means more agents spending your plan. harnsy Max shows your 5-hour and weekly limits as Claude Code and Codex report them on your computer, plus spend by agent and a daily budget.

Your phone, set up once.

Scan a QR code and sign in with a passkey (the hosted relay is in beta). A notification says which agent in which project is waiting; you read the question in the app. Prefer chat? The Telegram bot works without the relay. How we handle your data

Free harnsy: one organization, 2 projects, no limit on agents. harnsy Max: everything beyond that — more projects and organizations, your phone, and up to 3 machines.

Compare editions →

Why not Claude's Agent View?

If you work in Claude Code, use it. It comes with Claude Code, and it shows every background session across your projects on one screen. It's a research preview, and it alerts you in the terminal. harnsy Max is for the hours you're away: the question reaches your phone or chat, and you answer there. Checked Oct 19, 2026 · Claude Code docs, agent-view

harnsy is not affiliated with Anthropic. It works with the Claude plan you already have. Claude and Claude Code are trademarks of Anthropic.

Questions

What is a team of AI agents in harnsy?

AI programs such as Claude Code or Codex (or OpenCode), each given a role. A lead sets the task and picks who does it; roles message each other, hand work over and check it; you set the direction and accept the result. harnsy connects them and has no model of its own.

Who decides how a task is split: the lead or the role?

Either. The lead splits it, or gives it to a role that splits it for the roles under it, as the analyst does in the data team.

Do the agents work without a person?

No. You set the direction and answer the questions that need you. Your request always waits for your Accept. The lead checks the parts on the way. harnsy shows you what waits for you.

Can one team mix several AI programs?

Yes. Each role runs the AI program you choose: Claude Code, Codex, OpenCode or pi. Each role is an ordinary session of its program, so its own subagents work inside it as usual.

Do I pay for models separately?

Usually. harnsy has no model of its own. Claude Code, Codex, OpenCode and pi need a plan or key from Anthropic, OpenAI or another provider; you pay them, not us, and their terms apply to your use. The landing FAQ has the detail.

Where does my data go?

harnsy keeps its data on your machine, in ~/.harnsy, and has no telemetry. The AI programs you run (Claude Code, Codex, OpenCode, pi) send what they work on to their provider, under the provider’s terms. The landing FAQ lists exactly what harnsy sends and when.

Are the example teams real customers?

No. Three of the fields here are real runs of our own team. In two of them, water-supply design and the SaaS MVP, our crew plays the person; the web service is our own company’s work with its real founder. The others are illustrations, not customers and not results.

Start with one team today.

Needs Claude Code or Codex, signed in (their plans are paid separately)