ProgrammableMarketing/attunehq.com (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 8
  • This quarter · 11
  • Big bets · 3
  • Wildcards · 2
Generated Nov 10, 2026
  1. Programmable
  2. Playbooks
  3. Attune
Attune logo

growth playbook · Nov 10, 2026

attunehq.com (opens in a new tab)

Attune growth playbook

Diagnosis

Attune (YC Spring 2025, team of 3) ships good open-source tools fast: bastion and akari were updated the day before this review, and nudge is its most-starred repo. Its public story, though, is split across five places that disagree. The YC page, the launch post and the open founding-engineer role still sell hurry and faster builds.

The homepage has moved to applied AI for software engineering and no longer mentions hurry. hurry's sign-up site returns a 404. Two of the four homepage projects live on another domain without Attune's name. And the blog has been silent since January. This playbook first repairs the front doors (hurry's sign-up, one Attune home for every tool, a contact route, the YC profile, llms.txt and the GitHub org page).

It then turns shipping into attention: release posts, a measured bastion benchmark, a story that joins nudge, bastion and akari into one loop, design partners and a relaunch. Finally it tests revenue through hosted akari, a commercial licence and an opt-in report on agent runs.

Growth Score

5/10

Biggest Opportunity

Present nudge, bastion and akari as one agentic-engineering loop under the Attune name, and back it with measured results, so the stars and installs the tools already earn add up to one company people can find, follow and buy from.

Biggest Risk

Well-funded rivals (CodeRabbit and Greptile in AI review; Depot and Blacksmith in builds and CI) already own the search results and the buying conversations, and a three-person team spread across five tools may never give any one of them enough of a story to win.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    Give hurry a working front door: its README sends every new user to hurry.build for a token, and hurry.build returns a 404

    Today, point hurry.build at an attunehq.com/hurry page that explains hurry's status and offers the self-hosted path.

    High impact First result in 1 week
  2. 2

    Bring bastion and akari home: give each a page on attunehq.com and put Attune's name in their footers

    Add a "Built by Attune" footer link on bastion.tunas.dev and akari.tunas.dev.

    High impact First result in 2 weeks
  3. 3

    Add one way to reach Attune from the homepage: a contact line and a release-notes sign-up

    Add a contact line and email address to the homepage footer.

    High impact First result in 2 weeks

02

Your idea portfolio

24 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 8 ideas are marked Unexpected: plays you are unlikely to have tried.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 3Big bets · 8Fill-ins · 7Reconsider · 6
Effort →

Showing 24 of 24 ideas

This week 8

Quick wins with a clear first action.

  • 01

    hurry is the product Attune launched with. The YC page, the Launch YC post and the open founding-engineer role still lead with it ("Faster builds, zero effort", "up to 20x faster"), and with 55 stars it is Attune's second most-starred repo. Its README has one setup step: get an API token from hurry.build. When checked twice on November 10, 2026, hurry.build returned HTTP 404. The homepage no longer mentions hurry either. So every developer who arrives from YC, GitHub or a referral, keen to try the speed-up, hits a dead end at the one step that turns interest into a user.

    High impactLow effort First result in 1 week CEO

    First action

    Today, point hurry.build at an attunehq.com/hurry page that explains hurry's status and offers the self-hosted path.

    How to measure it

    Weekly hurry activations (tokens issued plus self-host installs)

    Now
    –
    Target
    From 0 to 10 a week
    By
    30 days

    Steps

    1. 1

      Restore or redirect

      Bring hurry.build back, or 301 it to attunehq.com/hurry.

      Cofounder, Engineering 2 hours

    2. 2

      Write the hurry page

      Status, supported Rust versions and platforms, managed versus self-hosted, and a token request.

      CEO 1 day

    3. 3

      Fix the README

      Point the token step at the working page; lead with self-hosting if the managed cache is paused.

      Founding Software Engineer 1 hour

    4. 4

      List hurry on the homepage

      Add it next to nudge, caliper, bastion and akari.

      Founding Software Engineer 1 hour

    5. 5

      Add uptime checks

      Monitor hurry.build and the token flow, with alerts to the team.

      Cofounder, Engineering 1 hour

    6. 6

      Tell past interest

      Reply to open issues and anyone who emailed about rollout that sign-up works again.

      CEO 1 day

    7. 7

      Measure

      Weekly tokens, self-host installs and page visits from GitHub and YC.

      CEO weekly

    First result
    1 week
    Cost
    $0 beyond a few hours of team time
    Owner
    CEO

    Smallest test

    Redirect hurry.build to a one-paragraph status page with the self-hosting link, and count clicks for a week.

    Why it works

    Within a week, make every path to hurry end somewhere that works. (1) Restore hurry.build, or redirect it to a new attunehq.com/hurry page. (2) On that page, state hurry's status honestly (alpha, Rust 1.92 and earlier, macOS ARM64 and Linux x86_64 first), give the two ways to start (request a managed-cache token, or self-host using the existing docs), and offer a short form or email for rollout help. (3) Update the README so the token step points to the working page and the self-hosting path comes first if the managed cache is paused. (4) List hurry on the homepage with the other projects. (5) Watch the page so a future outage is caught in hours, not months.

    Developers rarely report a dead sign-up link; they just leave. The demand already exists in the YC directory, the launch post and the GitHub stars, so a working page turns traffic Attune already earned into users and conversations at almost no cost, and it keeps the launch product from damaging trust in the newer tools.

    Ready to use

    Checklisthurry front-door checklist

    [ ] hurry.build loads or 301s to attunehq.com/hurry
    [ ] Page states status: alpha, Rust 1.92 and earlier, tier 1 platforms
    [ ] Two starts: request a managed-cache token, or self-host
    [ ] README token step points to the working page
    [ ] hurry listed on the attunehq.com homepage
    [ ] Uptime check on hurry.build and the token flow
    [ ] YC profile and launch post link to the same page

    Risks and how to handle them

    • The managed cache is deliberately paused

      Say so on the page and send people to self-hosting, which the repo already documents.

    • New users hit the Rust 1.93 limit

      State the supported versions above the install command (see idea 17).

    Evidence

    • hurry.buildhurry.build, where the hurry README sends new users for an API token, returned HTTP 404 both times it was checked on November 10, 2026.Source
    • GitHubhurry README: "Really, really fast builds"; in alpha; run hurry cargo build with an API token from hurry.build, or self-host; supports Rust 1.92 and earlier because Rust 1.93 removed a Cargo feature it relies on; 38 open issues and 6 open pull requests.Source
    • Y CombinatorYC company page: one-liner "Faster builds, zero effort."; moving from cargo build to hurry cargo build can make builds "up to 20x faster"; Rust now, Docker and other languages planned; founded 2025, Spring 2025 batch, team of 3, San Francisco; the founders previously led product at Teleport and engineering at FOSSA.Source
    • GitHubAttuneHQ organisation (November 10, 2026): 24 public repositories, 14 followers and no organisation bio. Stars: nudge 84, hurry 55, caliper 7, bastion 7, akari 7. bastion and akari were updated on November 9, 2026 and nudge on November 3; hurry was last updated on January 23, 2026.Source
    • Your websiteHomepage (checked November 10, 2026): "Attune is an applied AI company building the future of software engineering." It lists four projects, nudge and caliper (linked to GitHub) and bastion and akari (on tunas.dev subdomains), plus two posts. Hurry is not listed, and there is no contact route, email sign-up, team, customer, pricing or careers link.Source
  • 02

    bastion and akari are Attune's most active projects, both updated on November 9, 2026, but their sites live on tunas.dev. Neither site names Attune: bastion's footer carries an individual's copyright, and akari's GitHub link goes to a personal repository instead of attunehq. Neither README links to attunehq.com. A developer who likes bastion has no way to learn that the same team makes nudge and akari.

    High impactLow effort First result in 2 weeks Cofounder

    First action

    Add a "Built by Attune" footer link on bastion.tunas.dev and akari.tunas.dev.

    How to measure it

    Referral visits from bastion and akari sites

    Now
    –
    Target
    200 a month
    By
    60 days

    Steps

    1. 1

      Footer links

      "Built by Attune" with a link to attunehq.com on both sites.

      Cofounder, Engineering 1 hour

    2. 2

      Fix the GitHub link

      akari's site and README point to attunehq/akari.

      Cofounder, Engineering 1 hour

    3. 3

      Product pages

      attunehq.com/bastion and /akari, each with a pitch, install and docs.

      CEO 2 days

    4. 4

      Cross-links

      Each tool's site and README lists the other Attune tools.

      Founding Software Engineer 2 hours

    5. 5

      Plan the domain move

      Decide whether docs move under attunehq.com, with redirects.

      Cofounder, Engineering 1 day

    6. 6

      Measure

      Referral visits and cross-tool installs.

      CEO monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Cofounder, Engineering

    Smallest test

    Add the footer link to both sites today and count clicks for two weeks.

    Why it works

    Add attunehq.com/bastion and attunehq.com/akari, each with a one-paragraph pitch, the install command and links to the docs. Put "Built by Attune" with a link in both tunas.dev footers, and point akari's GitHub link and README at the attunehq repository. In the long run, move the docs to attunehq.com subpaths or subdomains so search and links build one domain.

    Every star and visit then builds the company brand rather than a separate one. Developers who trust one tool are the cheapest audience for the next.

    Risks and how to handle them

    • The tunas.dev sites are meant as independent projects

      Keep them, but make the Attune link explicit so the brand still gains.

    Evidence

    • bastion.tunas.devBastion: an open-source merge gate made of small reviewers declared in a checked-in .bastion.yaml. Gates block and advisors comment; it fails closed; the same reviewers run locally and in CI; it works with five agent backends using the team's existing auth and billing. AGPL-3.0, no pricing, a recall chart labelled illustrative, and a footer with an individual's copyright rather than Attune's name.Source
    • akari.tunas.devAkari: a self-hosted, searchable history of coding-agent sessions across machines, with cost per token by project, model and machine, A-F run grades, a read-only MCP endpoint, and public share links for sessions and usage overviews. It supports five agents, has no telemetry and is AGPL. The page does not name Attune, and its GitHub link goes to a personal repository rather than attunehq.Source
    • GitHubattunehq/akari README: install scripts and the server container image are served from a different GitHub account than attunehq; 235 commits, 7 stars, 5 forks and 8 open pull requests; no link to attunehq.com.Source
    • GitHubattunehq/bastion README: a CLI plus a GitHub Action merge gate; 173 commits, 7 stars and 13 open pull requests; links to bastion.tunas.dev but not to attunehq.com.Source
    • Your websiteHomepage (checked November 10, 2026): "Attune is an applied AI company building the future of software engineering." It lists four projects, nudge and caliper (linked to GitHub) and bastion and akari (on tunas.dev subdomains), plus two posts. Hurry is not listed, and there is no contact route, email sign-up, team, customer, pricing or careers link.Source
  • 03

    The YC company page, the Launch YC post and the open founding-engineer role all describe Attune as "Faster builds, zero effort", with hurry as the first product. Since November 2025 the homepage has instead said Attune is "an applied AI company building the future of software engineering", lists four agent and CI tools, and leaves hurry out. Investors, candidates and fellow founders who check YC first meet a different company from the one on the site.

    Medium impactLow effort First result in 2 weeks CEO

    First action

    Draft a new YC one-liner that names the agent-tool direction.

    How to measure it

    Founding-engineer applicants who mention the agent tools

    Now
    –
    Target
    5 a month
    By
    60 days

    Steps

    1. 1

      Write the one-liner

      One sentence covering agents and builds.

      CEO 1 hour

    2. 2

      Update the long description

      Current tools, current proof, link to attunehq.com.

      CEO 2 hours

    3. 3

      Update the job post

      The product paragraph and what the hire would own.

      CEO 1 hour

    4. 4

      Add a new launch

      A Launch YC for bastion or the agent-tool set.

      CEO 1 day

    5. 5

      Match the homepage

      Use the same words in the homepage meta description.

      Founding Software Engineer 1 hour

    6. 6

      Check quarterly

      Review every public profile for drift.

      CEO quarterly

    First result
    2 weeks
    Cost
    $0
    Owner
    CEO

    Smallest test

    Change the YC one-liner today and watch applicant quality for a month.

    Why it works

    Rewrite the YC one-liner and long description around the current direction: tools that bring rigour to agent-written code (nudge, bastion, akari), with hurry and caliper as the build side. Update the job post's product paragraph to match, and add a short note to the launch post, or a new launch, linking to the current homepage.

    The YC directory and job board are among the most-read pages about any YC company. One consistent story improves hiring replies, investor intros and partner trust within days.

    Risks and how to handle them

    • Dropping hurry from the story confuses existing users

      Keep hurry named as the build-speed tool and link its page (idea 1).

    Evidence

    • Y CombinatorYC company page: one-liner "Faster builds, zero effort."; moving from cargo build to hurry cargo build can make builds "up to 20x faster"; Rust now, Docker and other languages planned; founded 2025, Spring 2025 batch, team of 3, San Francisco; the founders previously led product at Teleport and engineering at FOSSA.Source
    • HiringFounding Software Engineer (YC job board, San Francisco, open on November 10, 2026): $150K-$200K and 0.50%-1.00% equity; mostly Rust; includes talking to customers and owning problems end to end; the post still says the first product is faster build tools that need zero migration effort, and cites over $4B a year spent by software teams on builds.Source
    • Site historyChange record since November 2025: the homepage headline moved from "Faster Builds Zero Effort" to "Attune Technologies, Inc.", and the site dropped Next.js, React and v0.dev.Source
    • Your websiteHomepage (checked November 10, 2026): "Attune is an applied AI company building the future of software engineering." It lists four projects, nudge and caliper (linked to GitHub) and bastion and akari (on tunas.dev subdomains), plus two posts. Hurry is not listed, and there is no contact route, email sign-up, team, customer, pricing or careers link.Source
  • 04

    The homepage has no contact route, no email sign-up, no team and no social profiles other than GitHub, and no newsletter, RSS feed or analytics tool was detected. The YC launch asked teams with slow builds to email the founders, and the founding role includes talking to customers, but a developer who reads the homepage and is interested has nowhere to go except GitHub.

    High impactLow effort First result in 2 weeks CEO

    First action

    Add a contact line and email address to the homepage footer.

    How to measure it

    Release-notes subscribers

    Now
    –
    Target
    300
    By
    90 days

    Steps

    1. 1

      Contact line

      One sentence and an email or form on the homepage and every post.

      CEO 1 hour

    2. 2

      Sign-up form

      "One email per release" with a choice of tools.

      Founding Software Engineer 1 day

    3. 3

      RSS feed

      For /blog.

      Founding Software Engineer 2 hours

    4. 4

      Analytics

      Privacy-friendly page and referral counts.

      Founding Software Engineer 2 hours

    5. 5

      Link from READMEs

      "Get release notes" in each tool's README.

      Cofounder, Engineering 1 hour

    6. 6

      Send the first issue

      Recent releases of bastion, akari and nudge.

      CEO 1 day

    First result
    2 weeks
    Cost
    Under $20 a month for an email tool
    Owner
    CEO

    Smallest test

    Add the contact line and count replies for two weeks.

    Why it works

    Add three things to the homepage and the blog: a line inviting teams to talk ("Using agents on a real codebase? Talk to us") with a short form or email; a release-notes sign-up (one email per release across all five tools); and an RSS feed for the blog. Add privacy-friendly analytics so the team can see which project pages people visit.

    Open-source interest is invisible until people can raise a hand. A sign-up list gives every future launch an audience on day one, and a contact line creates the customer conversations an early company needs.

    Risks and how to handle them

    • Developers dislike marketing email

      Only release notes, plain text, easy unsubscribe.

    Evidence

    • Your websiteHomepage (checked November 10, 2026): "Attune is an applied AI company building the future of software engineering." It lists four projects, nudge and caliper (linked to GitHub) and bastion and akari (on tunas.dev subdomains), plus two posts. Hurry is not listed, and there is no contact route, email sign-up, team, customer, pricing or careers link.Source
    • Site scanNo analytics tool, newsletter, RSS feed or social profile other than GitHub was detected on the site; zero Hacker News mentions of the domain; domain authority score 23.Source
    • Y CombinatorLaunch YC post "Attune - Faster Builds, Zero Effort": as AI speeds up writing code, slow builds become the bottleneck; existing fixes need costly migrations (such as to Bazel) or bigger servers; hurry offers "drop-in replacements for existing build tools"; the call to action is to email the founders.Source
    • HiringFounding Software Engineer (YC job board, San Francisco, open on November 10, 2026): $150K-$200K and 0.50%-1.00% equity; mostly Rust; includes talking to customers and owning problems end to end; the post still says the first product is faster build tools that need zero migration effort, and cites over $4B a year spent by software teams on builds.Source
  • 05

    Attune's users work inside coding agents, and those agents read llms.txt. Attune's llms.txt lists only four pages. Its Nudge entry repeats the company description instead of saying what Nudge does, and bastion, akari and hurry are missing. bastion and akari each publish their own llms.txt on tunas.dev, but the company file does not point to them.

    Medium impactLow effort First result in 1 month Founding Software Engineer

    First action

    Replace the Nudge entry with an accurate one-line description.

    How to measure it

    Visits referred by AI assistants

    Now
    –
    Target
    Measurable and growing
    By
    90 days

    Steps

    1. 1

      Fix Nudge

      One accurate line and install command.

      Founding Software Engineer 30 minutes

    2. 2

      Add the missing tools

      bastion, akari, hurry and caliper with docs links.

      Founding Software Engineer 1 hour

    3. 3

      Link sub-files

      Point to the tunas.dev llms.txt files.

      Founding Software Engineer 15 minutes

    4. 4

      Generate it

      Build from the homepage data so it updates itself.

      Founding Software Engineer 2 hours

    5. 5

      Test

      Ask three coding agents about each tool and compare answers.

      CEO 1 hour

    6. 6

      Re-check

      After every release.

      Founding Software Engineer per release

    First result
    1 month
    Cost
    $0
    Owner
    Founding Software Engineer

    Smallest test

    Fix the Nudge line today.

    Why it works

    Rewrite llms.txt with one accurate line per tool (what it does, who it is for, install command, docs link), linking to the bastion and akari llms.txt files and the hurry page. Generate it from the same source as the homepage so it cannot drift again.

    When a developer asks their agent "how do I gate merges on agent review?", the answer is drawn from files like this. A correct entry costs an hour and puts Attune's tools where its users already ask questions.

    Risks and how to handle them

    • Hard to measure

      Tag links in llms.txt and watch referral sources.

    Evidence

    • Your websitellms.txt lists four pages (home, posts, Caliper, Nudge). The Nudge entry repeats the company description instead of describing Nudge, and bastion, akari and hurry are absent.Source
    • bastion.tunas.devBastion: an open-source merge gate made of small reviewers declared in a checked-in .bastion.yaml. Gates block and advisors comment; it fails closed; the same reviewers run locally and in CI; it works with five agent backends using the team's existing auth and billing. AGPL-3.0, no pricing, a recall chart labelled illustrative, and a footer with an individual's copyright rather than Attune's name.Source
    • akari.tunas.devAkari: a self-hosted, searchable history of coding-agent sessions across machines, with cost per token by project, model and machine, A-F run grades, a read-only MCP endpoint, and public share links for sessions and usage overviews. It supports five agents, has no telemetry and is AGPL. The page does not name Attune, and its GitHub link goes to a personal repository rather than attunehq.Source
  • 06

    GitHub is the only social profile Attune has, and the org page is where nudge's 84 stargazers and hurry's 55 land when they click through. It has no bio, 14 followers and 24 repositories in date order, including forks and experiments, with the five products mixed among them.

    Medium impactLow effort First result in 2 weeks Cofounder

    First action

    Write the org bio and pin the five product repos.

    How to measure it

    GitHub org followers

    Now
    –
    Target
    From 14 to 100
    By
    90 days

    Steps

    1. 1

      Bio and link

      One line plus attunehq.com.

      Cofounder, Engineering 10 minutes

    2. 2

      Pin products

      nudge, bastion, akari, hurry, caliper.

      Cofounder, Engineering 10 minutes

    3. 3

      Profile README

      The loop, install lines, sign-up link.

      CEO 2 hours

    4. 4

      Tidy experiments

      Mark forks and toys as such in their descriptions.

      Founding Software Engineer 1 hour

    5. 5

      Topics

      Add repo topics such as coding-agents, code-review, rust and ci.

      Founding Software Engineer 30 minutes

    6. 6

      Track

      Followers and stars per month.

      CEO monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Cofounder, Engineering

    Smallest test

    Add the bio and pins today.

    Why it works

    Add an org bio and a link to attunehq.com, pin the five products, and add a profile README (.github/profile) that explains the loop (nudge, bastion, akari) and the build tools (hurry, caliper) with one install line each and a link to the release-notes sign-up.

    Developers judge a tools company by its GitHub page. A clear page turns a visit to one repo into a look at all five, and into followers who see future releases.

    Risks and how to handle them

    • Little change on its own

      Pair it with release posts (idea 9) that send people to the org.

    Evidence

    • GitHubAttuneHQ organisation (November 10, 2026): 24 public repositories, 14 followers and no organisation bio. Stars: nudge 84, hurry 55, caliper 7, bastion 7, akari 7. bastion and akari were updated on November 9, 2026 and nudge on November 3; hurry was last updated on January 23, 2026.Source
    • Site scanNo analytics tool, newsletter, RSS feed or social profile other than GitHub was detected on the site; zero Hacker News mentions of the domain; domain authority score 23.Source
    • GitHubnudge README: "a collaborative memory layer" for coding-agent hooks, with setup commands for four agents; rules, opt-in semantic rules, Bash substitutions, prompt reminders, learned incident notes stored as Markdown in Git, and nudge check for CI. Its only attunehq.com link is the January blog post, and there is no hosted service.Source
  • 07

    In Google's mobile lab test the homepage scores 92 but takes 3.3s to show its main content, against a 2.5s target, even though that content is a paragraph of text. Fonts are 151KB of a 325KB page, all from Google Fonts, and render-blocking requests cost about 0.75s. There is no real-visitor data yet, so this is a lab result. The page also has no social share image, so links posted in chat or on social show a bare preview.

    Low impactLow effort First result in 1 day Founding Software Engineer

    First action

    List the font weights actually used and remove the rest.

    How to measure it

    Mobile LCP (lab)

    Now
    –
    Target
    Under 2.5s
    By
    2 weeks

    Steps

    1. 1

      Audit fonts

      Weights and styles in use.

      Founding Software Engineer 30 minutes

    2. 2

      Self-host

      Subset woff2 with swap and preload.

      Founding Software Engineer 2 hours

    3. 3

      Share image

      One Open Graph image for the homepage and blog.

      CEO 1 hour

    4. 4

      Touch targets

      Fix the one accessibility issue.

      Founding Software Engineer 30 minutes

    5. 5

      Re-test

      PageSpeed mobile and desktop.

      Founding Software Engineer 15 minutes

    6. 6

      Apply to tool sites

      Same fixes on the tunas.dev sites if needed.

      Founding Software Engineer 2 hours

    First result
    1 day
    Cost
    $0
    Owner
    Founding Software Engineer

    Smallest test

    Self-host one font and re-run PageSpeed.

    Why it works

    Serve one or two font weights from the site itself with font-display: swap and a preload, drop unused weights, and add an Open Graph image showing the tool lineup. Re-run PageSpeed afterwards.

    Text-only pages should paint at once, and a proper preview makes every shared link look like a real product.

    Risks and how to handle them

    • Little business impact on its own

      Do it in one afternoon alongside idea 2.

    Evidence

    • PageSpeedGoogle PageSpeed (mobile, November 10, 2026): score 92 (desktop 100); lab LCP 3.3s against a 2.5s target, the largest element being a paragraph of text; render-blocking requests cost about 0.75s; fonts are 151KB of a 325KB page, all from Google Fonts; there is no real-visitor (field) data; one accessibility issue (touch target size); no social share image.Source
  • 19

    Attune is hiring a founding software engineer ($150K-$200K, 0.50%-1.00% equity, mostly Rust) through YC's job board, but attunehq.com has no careers page (/careers returns a 404) and no team page. The only description of the job describes last year's build-tool focus. The engineers most likely to fit are the ones already reading nudge, bastion and akari, and they have no route from the tools to the role.

    Medium impactLow effort First result in 2 weeks CEO

    First action

    Copy the YC role to /careers and rewrite the product paragraph.

    How to measure it

    Applicants referred by the careers page

    Now
    –
    Target
    10
    By
    60 days

    Steps

    1. 1

      Write the page

      Role, first 90 days, stack, pay range.

      CEO 2 hours

    2. 2

      Add work samples

      Links to good first issues in each repo.

      Cofounder, Engineering 1 hour

    3. 3

      Link it

      Homepage footer and READMEs.

      Founding Software Engineer 1 hour

    4. 4

      Match YC

      Same words on the YC job post.

      CEO 30 minutes

    5. 5

      Invite contributors

      A personal note to active issue authors.

      CEO 1 day

    6. 6

      Track

      Applicant source.

      CEO weekly

    First result
    2 weeks
    Cost
    $0
    Owner
    CEO

    Smallest test

    Add a "We're hiring" line to the homepage linking to the YC post.

    Why it works

    Add attunehq.com/careers with the role in Attune's current words: the agent tools, the Rust work, what the hire would own in the first 90 days, and links to the repos as a work sample. Link it from the homepage footer and from each README's contributing section.

    Contributors and power users make the best early hires, and a page in the company's own voice converts better than a directory listing.

    Risks and how to handle them

    • Too few applicants from a small audience

      Keep the YC listing live too.

    Builds on

    Evidence

    • Your websiteSitemap: four URLs in total (/, /blog, /blog/caliper, /blog/nudge), and /careers returns a 404. The blog's only two posts are dated January 12 and January 16, 2026.Source
    • HiringFounding Software Engineer (YC job board, San Francisco, open on November 10, 2026): $150K-$200K and 0.50%-1.00% equity; mostly Rust; includes talking to customers and owning problems end to end; the post still says the first product is faster build tools that need zero migration effort, and cites over $4B a year spent by software teams on builds.Source

This quarter 11

The core plays for the next three months.

  • 08

    nudge is Attune's most-starred repo. The only post about it (January 12, 2026) describes "just-in-time guardrails", names one supported agent and calls the tool not production-grade, and its Show HN got 4 points. The README now describes "a collaborative memory layer" with setup for four agents, semantic rules, Bash substitutions, prompt reminders, learned incident notes stored in Git and a CI check. The public story is ten months and several features behind the product.

    High impactMedium effort First result in 1 month CEO

    First action

    List every nudge feature added since January 12.

    How to measure it

    New nudge stars after the post

    Now
    –
    Target
    +150
    By
    60 days

    Steps

    1. 1

      List changes

      Features since January from the commit log.

      Cofounder, Engineering 2 hours

    2. 2

      Pick a real example

      A lesson nudge kept an agent from repeating.

      Cofounder, Engineering 1 day

    3. 3

      Write the post

      Problem, what is new, setup for four agents.

      CEO 3 days

    4. 4

      Update the README

      Link to the post; drop the old "not production-grade" framing if it no longer applies.

      Founding Software Engineer 1 hour

    5. 5

      Share

      Release-notes list, GitHub, developer communities.

      CEO 1 day

    6. 6

      Measure

      Stars, clones and issues opened.

      CEO weekly

    First result
    1 month
    Cost
    Staff time only
    Owner
    CEO

    Smallest test

    Publish a changelog-style post first and see how much traffic it gets.

    Why it works

    Write a new post, "nudge is now a memory layer for coding agents": the problem (agents forget project lessons), what is new since January, a before-and-after from Attune's own repos, setup for each of the four agents, and the CI check. Update the README to link to it, and use it as the anchor for idea 14's relaunch.

    Most of nudge's possible users last heard about it as an early guardrail tool. A post about what it does now gives them a reason to look again and gives the team something to share.

    Risks and how to handle them

    • Overclaiming maturity

      State plainly what is stable and what is experimental.

    Evidence

    • GitHubnudge README: "a collaborative memory layer" for coding-agent hooks, with setup commands for four agents; rules, opt-in semantic rules, Bash substitutions, prompt reminders, learned incident notes stored as Markdown in Git, and nudge check for CI. Its only attunehq.com link is the January blog post, and there is no hosted service.Source
    • Your websiteNudge post (January 12, 2026): "just-in-time guardrails" that re-prompt the agent when a rule matches; it names one supported agent, says Nudge is not yet production-grade, and asks readers to open issues.Source
    • Hacker NewsShow HN: Nudge - Enforcing guardrails for coding agents received 4 points.Source
  • 09

    The blog's only two posts are from January 12 and 16, 2026. Since then bastion (173 commits) and akari (235 commits) have been built and shipped, and both were updated on November 9, but neither has a post on attunehq.com. All that work has gone into the products and none into the company's site.

    Medium impactMedium effort First result in 1 month CEO

    First action

    Write the bastion launch post from its existing site copy.

    How to measure it

    Release posts published

    Now
    –
    Target
    2 a month
    By
    90 days

    Steps

    1. 1

      Template

      What changed, why, example, upgrade.

      CEO 1 hour

    2. 2

      bastion post

      The idea of small, fail-closed reviewers.

      CEO 2 days

    3. 3

      akari post

      Session replay, cost and run grades.

      CEO 2 days

    4. 4

      Release hook

      Each GitHub release links to its post.

      Cofounder, Engineering 1 hour

    5. 5

      Distribute

      Release-notes list and communities.

      CEO per post

    6. 6

      Review

      Which posts drive installs.

      CEO monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    CEO

    Smallest test

    Publish the bastion post this month.

    Why it works

    Adopt a simple rule: every notable release gets a 300-600 word post on attunehq.com covering what changed, why, one example and the upgrade command, which then goes to the release-notes list and the GitHub release. Start with launch posts for bastion and akari.

    Regular, concrete posts build search traffic, give subscribers a reason to stay and show buyers the tools are maintained, which is the first question anyone asks about early open-source tools.

    Risks and how to handle them

    • A three-person team has no writing time

      Draft from commit logs and keep posts short.

    Builds on

    Evidence

    • Your websiteSitemap: four URLs in total (/, /blog, /blog/caliper, /blog/nudge), and /careers returns a 404. The blog's only two posts are dated January 12 and January 16, 2026.Source
    • GitHubAttuneHQ organisation (November 10, 2026): 24 public repositories, 14 followers and no organisation bio. Stars: nudge 84, hurry 55, caliper 7, bastion 7, akari 7. bastion and akari were updated on November 9, 2026 and nudge on November 3; hurry was last updated on January 23, 2026.Source
    • GitHubattunehq/bastion README: a CLI plus a GitHub Action merge gate; 173 commits, 7 stars and 13 open pull requests; links to bastion.tunas.dev but not to attunehq.com.Source
    • GitHubattunehq/akari README: install scripts and the server container image are served from a different GitHub account than attunehq; 235 commits, 7 stars, 5 forks and 8 open pull requests; no link to attunehq.com.Source
  • 10

    bastion's central claim is that splitting review into many single-concern reviewers keeps recall high as coverage grows, but the chart on its site is labelled illustrative and shows no measured data. Its rivals lead with scale and customer numbers: CodeRabbit claims 17K customers, Greptile 22,000+ teams. A three-person open-source project cannot win on logos, but it can win on a reproducible measurement.

    High impactHigh effort First result in 6 weeks Cofounder

    First action

    Collect 50 merged PRs from Attune's repos where a later fix revealed a missed problem.

    How to measure it

    Teams installing bastion after the benchmark

    Now
    –
    Target
    25
    By
    90 days

    Steps

    1. 1

      Build the dataset

      PRs with known misses, labelled by concern.

      Cofounder, Engineering 2 weeks

    2. 2

      Write the harness

      Repeatable runs with fixed reviewer sets.

      Founding Software Engineer 1 week

    3. 3

      Run the sweep

      1, 5 and 15 reviewers; recall and false blocks.

      Founding Software Engineer 1 week

    4. 4

      Replace the chart

      Measured data on the bastion page.

      Cofounder, Engineering 1 day

    5. 5

      Publish openly

      Dataset, harness and write-up.

      CEO 1 week

    6. 6

      Invite submissions

      Other tools may run the same benchmark.

      CEO ongoing

    First result
    6 weeks
    Cost
    Agent usage for the runs plus about six weeks of part-time engineering
    Owner
    Cofounder, Engineering

    Smallest test

    Measure recall on 20 PRs with 1 versus 10 reviewers.

    Why it works

    Build a public benchmark: a set of real pull requests with known, seeded defects across several concerns (error handling, API compatibility, missing tests, docs drift). Run bastion with 1, 5 and 15 reviewers and plot recall and false blocks. Publish the dataset, the harness and the results, and invite other review tools to submit runs.

    Engineers trust numbers they can reproduce. A measured chart turns bastion's design argument into evidence and gives the relaunch (idea 14) a story.

    Risks and how to handle them

    • The results are weaker than the illustration

      Publish anyway and show the reviewer changes that improved them; honesty is the point.

    Evidence

    • bastion.tunas.devBastion: an open-source merge gate made of small reviewers declared in a checked-in .bastion.yaml. Gates block and advisors comment; it fails closed; the same reviewers run locally and in CI; it works with five agent backends using the team's existing auth and billing. AGPL-3.0, no pricing, a recall chart labelled illustrative, and a footer with an individual's copyright rather than Attune's name.Source
    • Competitor researchCodeRabbit: "The future isn't writing code. It's reviewing it."; claims 17K customers and 6M repositories.Source
    • Competitor researchGreptile: "The AI Code Reviewer", used by 22,000+ teams; free for qualified open-source projects, $1 per credit on Pro, and self-hosting with Docker Compose or Kubernetes.Source
  • 11

    akari can publish any session, or a usage overview, at a link anyone can open without an account. Those links are posted in team chats, issues and social threads, where the people reading them are exactly akari's next users. Attune has no other distribution channel beyond GitHub.

    Medium impactLow effort First result in 1 month Founding Software Engineer

    First action

    Add the footer to the shared-session template.

    How to measure it

    Referral visits from shared akari pages

    Now
    –
    Target
    100 a month
    By
    90 days

    Steps

    1. 1

      Design the footer

      One line, no logo clutter.

      Founding Software Engineer 1 hour

    2. 2

      Add to templates

      Shared sessions and public overviews.

      Founding Software Engineer 2 hours

    3. 3

      Add an off switch

      A server setting for self-hosters.

      Founding Software Engineer 2 hours

    4. 4

      Tag the link

      Referral parameter to the akari page.

      Founding Software Engineer 15 minutes

    5. 5

      Release note

      Explain the change openly.

      CEO 1 hour

    6. 6

      Measure

      Visits and installs from shared links.

      CEO monthly

    First result
    1 month
    Cost
    $0
    Owner
    Founding Software Engineer

    Smallest test

    Ship it in the next release and watch referral visits.

    Why it works

    Add a quiet footer to every shared page ("Shared with akari, self-hosted agent session history") linking to the akari page on attunehq.com with a referral tag. Let self-hosters switch it off, but make it on by default.

    Shared artefacts that name the tool spread it at zero cost, and every viewer has just seen a concrete example of what it does.

    Risks and how to handle them

    • Self-hosters see it as branding creep

      Keep it small, explain it, and make it easy to turn off.

    Builds on

    Evidence

    • akari.tunas.devAkari: a self-hosted, searchable history of coding-agent sessions across machines, with cost per token by project, model and machine, A-F run grades, a read-only MCP endpoint, and public share links for sessions and usage overviews. It supports five agents, has no telemetry and is AGPL. The page does not name Attune, and its GitHub link goes to a personal repository rather than attunehq.Source
    • Site scanNo analytics tool, newsletter, RSS feed or social profile other than GitHub was detected on the site; zero Hacker News mentions of the domain; domain authority score 23.Source
  • 12

    Attune's three agent tools fit together. nudge feeds project rules and learned lessons to the agent while it works, bastion runs narrow reviewers before a merge, and akari records and grades every run. The homepage lists them as four unrelated projects, and none of their READMEs mentions the others. Rivals each sell one piece, for example CodeRabbit and Greptile in review.

    High impactMedium effort First result in 1 month CEO

    First action

    Write down one real case where an akari finding became a nudge rule or bastion reviewer.

    How to measure it

    Multi-tool teams (from design partners and issues)

    Now
    –
    Target
    10
    By
    90 days

    Steps

    1. 1

      Find the example

      One real loop from Attune's own work.

      Cofounder, Engineering 2 days

    2. 2

      Draw the loop

      One diagram: rules, gate, learn.

      CEO 1 day

    3. 3

      Write the page

      attunehq.com/loop with install for all three.

      CEO 1 week

    4. 4

      Rework the homepage

      Lead with the loop.

      Founding Software Engineer 2 days

    5. 5

      Cross-link READMEs

      Each tool points to the next step.

      Founding Software Engineer 2 hours

    6. 6

      Measure

      Installs of a second tool.

      CEO monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    CEO

    Smallest test

    Publish the diagram and example as a post before reworking the homepage.

    Why it works

    Write one page and one post, "A feedback loop for agent-written code", showing the cycle: akari finds a failure pattern, it becomes a nudge rule or a bastion reviewer, and the next runs are cleaner. Use a real example from Attune's own repos. Rework the homepage around the loop, with hurry and caliper as the build side.

    A system is easier to remember and buy than five tools, and it raises the value of each install because the next tool is an obvious step.

    Risks and how to handle them

    • The tools do not yet hand data to each other

      Show the manual loop first, then build the links (for example, an akari export into nudge rules).

    Builds on

    Evidence

    • Your websiteHomepage (checked November 10, 2026): "Attune is an applied AI company building the future of software engineering." It lists four projects, nudge and caliper (linked to GitHub) and bastion and akari (on tunas.dev subdomains), plus two posts. Hurry is not listed, and there is no contact route, email sign-up, team, customer, pricing or careers link.Source
    • GitHubnudge README: "a collaborative memory layer" for coding-agent hooks, with setup commands for four agents; rules, opt-in semantic rules, Bash substitutions, prompt reminders, learned incident notes stored as Markdown in Git, and nudge check for CI. Its only attunehq.com link is the January blog post, and there is no hosted service.Source
    • bastion.tunas.devBastion: an open-source merge gate made of small reviewers declared in a checked-in .bastion.yaml. Gates block and advisors comment; it fails closed; the same reviewers run locally and in CI; it works with five agent backends using the team's existing auth and billing. AGPL-3.0, no pricing, a recall chart labelled illustrative, and a footer with an individual's copyright rather than Attune's name.Source
    • akari.tunas.devAkari: a self-hosted, searchable history of coding-agent sessions across machines, with cost per token by project, model and machine, A-F run grades, a read-only MCP endpoint, and public share links for sessions and usage overviews. It supports five agents, has no telemetry and is AGPL. The page does not name Attune, and its GitHub link goes to a personal repository rather than attunehq.Source
  • 13

    The caliper post benchmarked a single Rust build (InfluxDB): going from 2 to 4 CPUs cut build time from about 6m to 3.5m, gains faded past 16 CPUs, and 8GB of RAM was enough. The post itself warns that JavaScript, Python, Go and Java builds will differ. Runner vendors such as Blacksmith (60% cheaper than GitHub runners) and Depot (10x faster cached builds) sell on speed and cost, but none publishes neutral sizing data by stack.

    Medium impactMedium effort First result in 1 month Founding Software Engineer

    First action

    Pick one popular project per stack.

    How to measure it

    caliper stars

    Now
    –
    Target
    From 7 to 150
    By
    90 days

    Steps

    1. 1

      Pick projects

      One per stack: JavaScript, Python, Go, Java and another Rust project.

      Founding Software Engineer 1 day

    2. 2

      Run matrices

      CPU and RAM sweep, 10 runs each.

      Founding Software Engineer 1 week

    3. 3

      Add cost

      Per-build cost at list runner prices.

      Founding Software Engineer 2 days

    4. 4

      Publish the table

      A page plus raw data.

      CEO 3 days

    5. 5

      Share

      Each project's community and platform-engineering forums.

      CEO 1 week

    6. 6

      Refresh

      Each quarter, and accept community runs.

      Founding Software Engineer quarterly

    First result
    1 month
    Cost
    A few hundred dollars of server time
    Owner
    Founding Software Engineer

    Smallest test

    Add one Go project to the existing post.

    Why it works

    Run caliper's matrix mode on five well-known open-source projects, one per stack, and publish a table showing the sweet spot in CPUs and RAM, cost per build at common runner prices, and the point where adding cores stops helping. Keep the table as a page that is updated each quarter, and link it from the caliper README.

    "What size runner do I need for a Go build?" is a question every platform engineer asks. A neutral, reproducible table earns links and searches, and every row shows off caliper.

    Risks and how to handle them

    • Results depend on hardware

      Publish the hardware and invite reruns on other machines.

    Evidence

    • Your websiteCaliper post (January 16, 2026): benchmarks a build across CPU and RAM limits in Docker. On an InfluxDB Rust build (25 configurations, 10 runs each), going from 2 to 4 CPUs cut build time from about 6m to 3.5m, gains faded past 16 CPUs, and 8GB of RAM was enough. The post warns that JavaScript, Python, Go and Java builds will differ.Source
    • Competitor researchBlacksmith: a "drop-in replacement" for GitHub Actions runners claiming 60% lower cost, 3,000 free minutes a month and 10,000+ organisations.Source
    • Competitor researchDepot: software delivery infrastructure "built for machine scale" for teams shipping with agents; claims 10x faster builds with a shared cache and 40x faster container builds.Source
  • 14

    Attune's one Show HN, for nudge, got 4 points, and the domain has no Hacker News mentions. The post introduced a tool. What developer audiences reward is a result they can check. bastion's fail-closed, small-reviewer design is a strong argument, and with measured recall (idea 10) it becomes a finding rather than a product launch.

    High impactMedium effort First result in 1 day CEO

    First action

    Draft the title and the first comment explaining the method.

    How to measure it

    bastion stars in the launch week

    Now
    –
    Target
    +200
    By
    launch week

    Steps

    1. 1

      Finish the benchmark

      Idea 10 must be complete.

      Cofounder, Engineering see idea 10

    2. 2

      Write the post

      Method, result, limitations.

      CEO 3 days

    3. 3

      Prepare answers

      Cost, false blocks, self-hosting, licence.

      CEO 1 day

    4. 4

      Post and stay

      Team answers comments all day.

      CEO 1 day

    5. 5

      Launch YC

      Same story to the YC community.

      CEO 1 day

    6. 6

      Follow up

      Write up the questions people asked.

      CEO 1 week

    First result
    1 day after launch
    Cost
    Staff time only
    Owner
    CEO

    Smallest test

    Share the benchmark draft with five engineers first and refine the title.

    Why it works

    Once the benchmark is out, post it as "Show HN: we measured whether many narrow AI reviewers catch more than one big one", linking to the write-up, dataset and bastion. Have the team available for questions all day, and send the post to the release-notes list. Use the same piece for a new Launch YC.

    A reproducible result gives readers something to discuss and test, and every reply is a chance to explain bastion's design.

    Risks and how to handle them

    • Low traction again

      The write-up still serves as the bastion page and the outreach piece for design partners.

    Builds on

    Evidence

    • Hacker NewsShow HN: Nudge - Enforcing guardrails for coding agents received 4 points.Source
    • bastion.tunas.devBastion: an open-source merge gate made of small reviewers declared in a checked-in .bastion.yaml. Gates block and advisors comment; it fails closed; the same reviewers run locally and in CI; it works with five agent backends using the team's existing auth and billing. AGPL-3.0, no pricing, a recall chart labelled illustrative, and a footer with an individual's copyright rather than Attune's name.Source
    • Site scanNo analytics tool, newsletter, RSS feed or social profile other than GitHub was detected on the site; zero Hacker News mentions of the domain; domain authority score 23.Source
  • 15

    Teams looking at AI code review find CodeRabbit (17K customers claimed) and Greptile (22,000+ teams, $1 per credit, self-hosting) first. bastion differs in ways buyers care about: review policy lives in a checked-in .bastion.yaml under CODEOWNERS, the same reviewers run locally and in CI, gates fail closed, and it uses the team's existing agent auth and billing. None of this is written up as a comparison anywhere.

    Medium impactMedium effort First result in 1 month CEO

    First action

    List the five differences and check each against the rivals' current sites.

    How to measure it

    bastion installs referred by the page

    Now
    –
    Target
    20 a month
    By
    90 days

    Steps

    1. 1

      Check facts

      Each rival's current pages.

      CEO 1 day

    2. 2

      Write the page

      A fair table plus where bastion is weaker.

      CEO 3 days

    3. 3

      Add examples

      A sample .bastion.yaml and a fail-closed case.

      Cofounder, Engineering 1 day

    4. 4

      Review claims

      Trademarks and accuracy.

      CEO 1 day

    5. 5

      Publish

      On attunehq.com, linked from bastion's site.

      Founding Software Engineer 2 hours

    6. 6

      Refresh

      Each quarter.

      CEO quarterly

    First result
    1 month
    Cost
    Staff time only
    Owner
    CEO

    Smallest test

    Publish the table as a section on the bastion page first.

    Why it works

    Publish a factual "bastion and hosted AI reviewers" page: where policy lives, what happens when a reviewer fails, local and CI parity, cost model, self-hosting and licence. Say plainly where the hosted tools are stronger (setup, scale, codebase context). Date the page and cite each rival's own pages.

    Comparison searches are high-intent, and a fair page builds trust with sceptical engineers more than a feature list does.

    Risks and how to handle them

    • Out-of-date claims

      Date the page and link sources.

    Builds on

    Evidence

    • bastion.tunas.devBastion: an open-source merge gate made of small reviewers declared in a checked-in .bastion.yaml. Gates block and advisors comment; it fails closed; the same reviewers run locally and in CI; it works with five agent backends using the team's existing auth and billing. AGPL-3.0, no pricing, a recall chart labelled illustrative, and a footer with an individual's copyright rather than Attune's name.Source
    • Competitor researchCodeRabbit: "The future isn't writing code. It's reviewing it."; claims 17K customers and 6M repositories.Source
    • Competitor researchGreptile: "The AI Code Reviewer", used by 22,000+ teams; free for qualified open-source projects, $1 per credit on Pro, and self-hosting with Docker Compose or Kubernetes.Source
  • 16

    Attune has no published customers or case studies. The founding role includes talking to customers, and the three agent tools are free, self-hosted and work with the agents teams already use. What is missing is proof from teams outside Attune of what changes when rules, gates and run history are used together.

    High impactMedium effort First result in 6 weeks CEO

    First action

    List 20 teams already using two or more of the supported agents and contact the first ten.

    How to measure it

    Design-partner case studies

    Now
    –
    Target
    3 published
    By
    90 days

    Steps

    1. 1

      Shortlist

      20 teams from GitHub issues, stargazers and the YC network.

      CEO 3 days

    2. 2

      Invite

      A personal note with a clear one-month offer.

      CEO 1 week

    3. 3

      Onboard

      Set up all three tools with each team.

      Founding Software Engineer 1 week

    4. 4

      Baseline

      akari overview at the start.

      Founding Software Engineer 1 day each

    5. 5

      Weekly calls

      Issues, rules added, merges blocked.

      Cofounder, Engineering weekly

    6. 6

      Write up

      Before and after, with the team's approval.

      CEO 1 week

    First result
    6 weeks
    Cost
    Team time only
    Owner
    CEO

    Smallest test

    Run one partner for two weeks.

    Why it works

    Invite five teams that ship heavily with coding agents to a one-month programme: help with setup, a weekly 30-minute call, and a shared akari overview before and after. In return, ask for a short write-up of results (fewer repeated mistakes, blocked bad merges, agent spend) and permission to publish it.

    Five honest case studies prove the product to the next fifty teams, and the calls tell the team what to build and what people would pay for.

    Risks and how to handle them

    • Partners drop out

      Recruit eight to keep five.

    Builds on

    Evidence

    • HiringFounding Software Engineer (YC job board, San Francisco, open on November 10, 2026): $150K-$200K and 0.50%-1.00% equity; mostly Rust; includes talking to customers and owning problems end to end; the post still says the first product is faster build tools that need zero migration effort, and cites over $4B a year spent by software teams on builds.Source
    • bastion.tunas.devBastion: an open-source merge gate made of small reviewers declared in a checked-in .bastion.yaml. Gates block and advisors comment; it fails closed; the same reviewers run locally and in CI; it works with five agent backends using the team's existing auth and billing. AGPL-3.0, no pricing, a recall chart labelled illustrative, and a footer with an individual's copyright rather than Attune's name.Source
    • akari.tunas.devAkari: a self-hosted, searchable history of coding-agent sessions across machines, with cost per token by project, model and machine, A-F run grades, a read-only MCP endpoint, and public share links for sessions and usage overviews. It supports five agents, has no telemetry and is AGPL. The page does not name Attune, and its GitHub link goes to a personal repository rather than attunehq.Source
    • GitHubnudge README: "a collaborative memory layer" for coding-agent hooks, with setup commands for four agents; rules, opt-in semantic rules, Bash substitutions, prompt reminders, learned incident notes stored as Markdown in Git, and nudge check for CI. Its only attunehq.com link is the January blog post, and there is no hosted service.Source
  • 17

    hurry supports Rust 1.92 and earlier because Rust 1.93 removed a Cargo feature it relies on, and the repo has 38 open issues and has not been updated since January 23, 2026. As teams move to newer toolchains, every new visitor will find hurry doesn't work for them. Meanwhile the YC page still promises builds "up to 20x faster".

    Medium impactMedium effort First result in 3 weeks Cofounder

    First action

    Estimate the work for option (a) against current demand from issues and token requests.

    How to measure it

    Open hurry issues with a response

    Now
    –
    Target
    100%
    By
    30 days

    Steps

    1. 1

      Size the fix

      Effort to support Rust 1.93+.

      Cofounder, Engineering 3 days

    2. 2

      Check demand

      Token requests, issues, partner interest.

      CEO 2 days

    3. 3

      Decide

      Rebuild, pin or pause.

      CEO 1 day

    4. 4

      Update the README

      Status at the very top.

      Founding Software Engineer 1 hour

    5. 5

      Triage issues

      Label, answer or close all 38.

      Founding Software Engineer 2 days

    6. 6

      Update YC

      Match the claim to the decision.

      CEO 1 hour

    First result
    3 weeks
    Cost
    Engineering time, depending on the option
    Owner
    Cofounder, Engineering

    Smallest test

    Add a one-line status banner to the README today.

    Why it works

    Make a clear call within three weeks: (a) rebuild on a supported Cargo interface and publish a date, (b) keep hurry for pinned toolchains and say so, or (c) mark it paused, point to caliper and self-hosting, and archive the repo with a note. Whatever the choice, put it at the top of the README and on the hurry page from idea 1, and triage the open issues accordingly.

    A clear status keeps the trust earned at launch. An unclear one costs it with every developer who finds out for themselves that hurry doesn't run.

    Risks and how to handle them

    • Pausing hurry reads as failure

      Frame it as focus on the agent tools, with self-hosting still available.

    Builds on

    Evidence

    • GitHubhurry README: "Really, really fast builds"; in alpha; run hurry cargo build with an API token from hurry.build, or self-host; supports Rust 1.92 and earlier because Rust 1.93 removed a Cargo feature it relies on; 38 open issues and 6 open pull requests.Source
    • GitHubAttuneHQ organisation (November 10, 2026): 24 public repositories, 14 followers and no organisation bio. Stars: nudge 84, hurry 55, caliper 7, bastion 7, akari 7. bastion and akari were updated on November 9, 2026 and nudge on November 3; hurry was last updated on January 23, 2026.Source
    • Y CombinatorYC company page: one-liner "Faster builds, zero effort."; moving from cargo build to hurry cargo build can make builds "up to 20x faster"; Rust now, Docker and other languages planned; founded 2025, Spring 2025 batch, team of 3, San Francisco; the founders previously led product at Teleport and engineering at FOSSA.Source
  • 18

    nudge only helps once a team has written rules and incident notes. The January post says the team often has an agent draft the rules, and points to the rules in Attune's own hurry repo as the example. A new user starts with an empty folder, which is where most open-source tools lose people.

    Medium impactMedium effort First result in 1 month Cofounder

    First action

    Extract the rules Attune uses in its own Rust repos into a starter pack.

    How to measure it

    Pack installs

    Now
    –
    Target
    200
    By
    90 days

    Steps

    1. 1

      Extract rules

      From Attune's own repos.

      Cofounder, Engineering 3 days

    2. 2

      Test packs

      Low false positives on popular repos.

      Founding Software Engineer 1 week

    3. 3

      Install command

      One-line add for a pack.

      Founding Software Engineer 3 days

    4. 4

      Write three more packs

      TypeScript, Python, Go.

      Founding Software Engineer 2 weeks

    5. 5

      Open contributions

      Pack template and review rules.

      Cofounder, Engineering 2 days

    6. 6

      List and promote

      A packs page and release post.

      CEO 2 days

    First result
    1 month
    Cost
    Engineering time
    Owner
    Cofounder, Engineering

    Smallest test

    Publish the Rust pack in the README and count installs.

    Why it works

    Publish curated starter packs (Rust, TypeScript, Python, Go) of tested rules and Bash substitutions taken from Attune's own repos and design partners, installable with one command, for example nudge add rust-starter. Accept community packs through pull requests and list them on a page.

    A useful first session is the strongest predictor of a tool being kept, and community packs give users a reason to come back and contribute.

    Risks and how to handle them

    • Generic rules annoy teams

      Keep packs small and easy to edit, and mark each rule's purpose.

    Evidence

    • GitHubnudge README: "a collaborative memory layer" for coding-agent hooks, with setup commands for four agents; rules, opt-in semantic rules, Bash substitutions, prompt reminders, learned incident notes stored as Markdown in Git, and nudge check for CI. Its only attunehq.com link is the January blog post, and there is no hosted service.Source
    • Your websiteNudge post (January 12, 2026): "just-in-time guardrails" that re-prompt the agent when a rule matches; it names one supported agent, says Nudge is not yet production-grade, and asks readers to open issues.Source

Big bets 3

Larger plays that can change the trajectory.

  • 20

    akari is one server binary backed by Postgres, run with Docker Compose, plus a client on each machine. That suits individual developers, but a team lead who wants agent spend and run grades across 30 engineers has to own a database and a server first. Greptile shows the opposite model works in this market: hosted by default, self-hosting for enterprises. Attune has no paid product today.

    High impactHigh effort First result in 2 quarters CEO

    First action

    Ask the design partners whether they would pay for a hosted server, and how much.

    How to measure it

    Paying akari Cloud teams

    Now
    –
    Target
    5
    By
    2 quarters

    Steps

    1. 1

      Validate price

      Ten conversations with team leads.

      CEO 2 weeks

    2. 2

      Multi-tenant setup

      Isolated databases per team.

      Cofounder, Engineering 4 weeks

    3. 3

      Access and retention

      SSO, roles, deletion settings.

      Founding Software Engineer 3 weeks

    4. 4

      Paperwork

      Terms, privacy and DPA for transcript data.

      CEO 2 weeks

    5. 5

      Paid beta

      Design partners first.

      CEO 1 month

    6. 6

      Public launch

      Pricing page on attunehq.com.

      CEO 1 week

    First result
    2 quarters
    Cost
    Hosting plus a quarter of engineering
    Owner
    CEO

    Smallest test

    Host akari by hand for one design partner and invoice them.

    Why it works

    Offer akari Cloud: the same open-source server, hosted by Attune, priced per active developer, with SSO, retention settings and a data-processing agreement. Keep self-hosting free and identical. Start with the design partners (idea 16) as paying beta users.

    Agent spend is a new, growing line item that managers want to see, and hosting removes the one obstacle between a team's interest and a paid account.

    Risks and how to handle them

    • Transcripts contain sensitive code

      Strong isolation, retention controls and a clear data policy; keep self-hosting first-class.

    Builds on

    Evidence

    • akari.tunas.devAkari: a self-hosted, searchable history of coding-agent sessions across machines, with cost per token by project, model and machine, A-F run grades, a read-only MCP endpoint, and public share links for sessions and usage overviews. It supports five agents, has no telemetry and is AGPL. The page does not name Attune, and its GitHub link goes to a personal repository rather than attunehq.Source
    • GitHubattunehq/akari README: install scripts and the server container image are served from a different GitHub account than attunehq; 235 commits, 7 stars, 5 forks and 8 open pull requests; no link to attunehq.com.Source
    • Competitor researchGreptile: "The AI Code Reviewer", used by 22,000+ teams; free for qualified open-source projects, $1 per credit on Pro, and self-hosting with Docker Compose or Kubernetes.Source
  • 21

    bastion and akari are licensed AGPL-3.0, while nudge, hurry and caliper are Apache-2.0. Many companies' open-source policies limit or forbid AGPL software, so the teams most able to pay may be the ones that cannot adopt these two tools as they are. A commercial licence is a standard way to turn that obstacle into revenue without closing the code.

    High impactMedium effort First result in 1 quarter CEO

    First action

    Audit the contributors to both repos and get legal advice on relicensing rights.

    How to measure it

    Signed commercial licences

    Now
    –
    Target
    3
    By
    2 quarters

    Steps

    1. 1

      Rights audit

      Contributors and copyright ownership.

      Cofounder, Engineering 1 week

    2. 2

      Legal advice

      Licence text and CLA.

      CEO 3 weeks

    3. 3

      Add a CLA

      For future pull requests.

      Cofounder, Engineering 1 day

    4. 4

      Price it

      Simple bands by company size.

      CEO 1 week

    5. 5

      Publish the page

      "Using bastion and akari at work".

      CEO 2 days

    6. 6

      Offer to partners

      Design partners and inbound leads.

      CEO ongoing

    First result
    1 quarter
    Cost
    Legal fees for the licence and CLA
    Owner
    CEO

    Smallest test

    Add a line to both READMEs: "Need a non-AGPL licence? Contact us", and count requests.

    Why it works

    Publish a simple commercial licence for bastion and akari (an annual fee by company size, with support and a warranty), and a "Using bastion at work" page that explains the options. First, confirm that Attune holds the rights to relicense: check the contributor history and add a contributor licence agreement for future pull requests.

    It keeps the open-source reach while giving procurement a route to yes, and it gives Attune a revenue line that needs no new product.

    Risks and how to handle them

    • Community sees a CLA as a step towards closing the code

      Commit publicly to keeping the AGPL versions complete.

    Evidence

    • bastion.tunas.devBastion: an open-source merge gate made of small reviewers declared in a checked-in .bastion.yaml. Gates block and advisors comment; it fails closed; the same reviewers run locally and in CI; it works with five agent backends using the team's existing auth and billing. AGPL-3.0, no pricing, a recall chart labelled illustrative, and a footer with an individual's copyright rather than Attune's name.Source
    • akari.tunas.devAkari: a self-hosted, searchable history of coding-agent sessions across machines, with cost per token by project, model and machine, A-F run grades, a read-only MCP endpoint, and public share links for sessions and usage overviews. It supports five agents, has no telemetry and is AGPL. The page does not name Attune, and its GitHub link goes to a personal repository rather than attunehq.Source
    • GitHubAttuneHQ organisation (November 10, 2026): 24 public repositories, 14 followers and no organisation bio. Stars: nudge 84, hurry 55, caliper 7, bastion 7, akari 7. bastion and akari were updated on November 9, 2026 and nudge on November 3; hurry was last updated on January 23, 2026.Source
  • 22

    akari already grades every run from the transcript (outcome, an A-F grade from tool failures, retries and edit churn, plus prompt and context health) and prices every token. Across many teams that would be a unique dataset on how agent-written code really goes. akari promises no telemetry, so this can only be opt-in, and asking openly is part of the story.

    High impactHigh effort First result in 1 quarter CEO

    First action

    Publish a first report from Attune's own akari data.

    How to measure it

    Installs contributing aggregates

    Now
    –
    Target
    50
    By
    2 quarters

    Steps

    1. 1

      First report

      Attune's own runs, with method.

      CEO 3 weeks

    2. 2

      Design the opt-in

      Aggregates only, off by default.

      Cofounder, Engineering 2 weeks

    3. 3

      Privacy review

      Publish exactly what is sent.

      CEO 1 week

    4. 4

      Build the pipeline

      Collection and anonymisation.

      Founding Software Engineer 3 weeks

    5. 5

      Publish quarterly

      Report, charts and raw aggregates.

      CEO quarterly

    6. 6

      Pitch

      Newsletters and conference talks.

      CEO ongoing

    First result
    1 quarter
    Cost
    Engineering time and hosting for the collector
    Owner
    CEO

    Smallest test

    Publish one chart from Attune's own runs as a post.

    Why it works

    Add an explicit, off-by-default "contribute anonymous aggregates" setting that sends only summary statistics (grades, retry rates, cost per successful run, by language and agent type) and never code or prompts. Publish a quarterly "State of agent runs" report with the method and raw aggregates. Start with Attune's own runs and the design partners.

    Original data is what press, newsletters and conference talks cite, and every chart advertises the tool that measured it.

    Risks and how to handle them

    • It looks like a step back from "no telemetry"

      Off by default, open code, and a published list of exactly what is sent.

    Builds on

    Evidence

    • akari.tunas.devAkari: a self-hosted, searchable history of coding-agent sessions across machines, with cost per token by project, model and machine, A-F run grades, a read-only MCP endpoint, and public share links for sessions and usage overviews. It supports five agents, has no telemetry and is AGPL. The page does not name Attune, and its GitHub link goes to a personal repository rather than attunehq.Source

Wildcards 2

Unexpected experiments, each with a cheap way to test it.

  • 23

    pivotgpt is Attune's joke startup-pivot generator built from recent YC batches, live at pivotgpt.ceo with share-to-X links. It is designed to spread among founders and engineers, but the live page never mentions Attune and only links to the GitHub source.

    Low impactLow effort First result in 1 week Founding Software Engineer

    First action

    Add the footer line and a tagged link.

    How to measure it

    Referral visits from pivotgpt.ceo

    Now
    –
    Target
    Measurable
    By
    30 days

    Steps

    1. 1

      Add footer

      One line with a tagged link.

      Founding Software Engineer 15 minutes

    2. 2

      Share text

      Mention Attune in the share message.

      Founding Software Engineer 15 minutes

    3. 3

      Repo description

      Link to attunehq.com.

      Founding Software Engineer 5 minutes

    4. 4

      Reshare

      Post it again in YC and founder communities.

      CEO 1 hour

    5. 5

      Measure

      Tagged visits.

      CEO monthly

    6. 6

      Repeat

      Credit lines on any future side projects.

      CEO ongoing

    First result
    1 week
    Cost
    $0
    Owner
    Founding Software Engineer

    Smallest test

    Add the footer today.

    Why it works

    Add one footer line: "Made by Attune, tools for agent-written code" with a tagged link to attunehq.com. Optionally add a playful line next to the share button pointing to the loop page (idea 12).

    Humour spreads further than product posts, and a credit line turns every share into a small mention of Attune.

    Risks and how to handle them

    • The joke feels off-brand

      Keep the credit line plain and small.

    Evidence

    • GitHubpivotgpt: a satirical startup-pivot generator built from recent YC batches, live at pivotgpt.ceo with share-to-X links; the live page never mentions Attune and links only to the GitHub source.Source
    • Site scanNo analytics tool, newsletter, RSS feed or social profile other than GitHub was detected on the site; zero Hacker News mentions of the domain; domain authority score 23.Source
  • 24

    Attune owns both halves of a build-cost answer: caliper shows the right runner size (on InfluxDB, 4-8 CPUs and 8GB of RAM were the sweet spot), and hurry cuts the work each build does. Attune's own job post cites over $4B a year spent by software teams on builds. Nobody offers Rust teams a simple, neutral check of what they are overpaying.

    Medium impactMedium effort First result in 1 month Cofounder

    First action

    Write the one-page report template and offer the first three audits to the release-notes list.

    How to measure it

    Completed CI bill checks

    Now
    –
    Target
    10
    By
    90 days

    Steps

    1. 1

      Report template

      Size, cost, cache hits, savings.

      Cofounder, Engineering 2 days

    2. 2

      Offer audits

      Ten slots via the list and GitHub.

      CEO 1 week

    3. 3

      Run caliper

      On each team's main build.

      Founding Software Engineer 1 day each

    4. 4

      Trial hurry

      Two weeks, managed or self-hosted.

      Founding Software Engineer 2 weeks

    5. 5

      Send reports

      One page per team.

      Cofounder, Engineering 1 day each

    6. 6

      Publish results

      Anonymised summary post.

      CEO 1 week

    First result
    1 month
    Cost
    Team time and a little compute
    Owner
    Cofounder, Engineering

    Smallest test

    Run one audit for a friendly team.

    Why it works

    Offer ten Rust teams a free audit: run caliper on their main build, trial hurry (managed or self-hosted) for two weeks, and send a one-page report showing current runner size, recommended size, cache hit rate and estimated monthly savings. Publish anonymised results as a post, and turn the report into a self-serve command.

    A concrete savings number opens doors with engineering managers, and it gives hurry real users and data before the Rust 1.93 decision (idea 17).

    Risks and how to handle them

    • hurry fails on newer toolchains

      Pick teams on Rust 1.92 or earlier, or run caliper only.

    Builds on

    Evidence

    • Your websiteCaliper post (January 16, 2026): benchmarks a build across CPU and RAM limits in Docker. On an InfluxDB Rust build (25 configurations, 10 runs each), going from 2 to 4 CPUs cut build time from about 6m to 3.5m, gains faded past 16 CPUs, and 8GB of RAM was enough. The post warns that JavaScript, Python, Go and Java builds will differ.Source
    • GitHubhurry README: "Really, really fast builds"; in alpha; run hurry cargo build with an API token from hurry.build, or self-host; supports Rust 1.92 and earlier because Rust 1.93 removed a Cargo feature it relies on; 38 open issues and 6 open pull requests.Source
    • HiringFounding Software Engineer (YC job board, San Francisco, open on November 10, 2026): $150K-$200K and 0.50%-1.00% equity; mostly Rust; includes talking to customers and owning problems end to end; the post still says the first product is faster build tools that need zero migration effort, and cites over $4B a year spent by software teams on builds.Source
More example playbooks and reviews

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • Striveworks growth strategyAI operations software: the Chariot platform builds, deploys, monitors and remediates AI models from cloud to disconnected edge, and…20 growth ideas
  • Trust Wallet growth strategyA self-custody crypto wallet for iOS, Android and the browser across 100+ blockchains, with swaps, buying through third-party providers…22 growth ideas
  • SanMar growth strategyA family-owned wholesale supplier of blank apparel, bags, headwear and accessories, with national brands and its own private labels…21 growth ideas
  • FLORA growth strategyA node-based creative workspace where designers, brand teams and agencies generate and edit images, video, audio and 3D with 50+ models on…21 growth ideas
  • fonio growth strategyAI phone agents for small and medium-sized businesses that answer calls around the clock, book appointments and pass on messages, plus…21 growth ideas
  • Centex Auto Title growth strategyA privately owned, Travis County and Texas DMV authorized full-service deputy in Austin: title transfers, registration and renewals…22 growth ideas
  • VESSL AI growth strategyA specialized AI cloud (VESSL Cloud) that sources and routes GPU capacity across clusters and providers: self-serve A100, H100 and L40S by…23 growth ideas
  • Whippy growth strategyAn AI-native business communication platform (texting, calling, email, AI voice agents, AI recruiting and workflows) with deep ATS…20 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on November 10, 2026, and cites them throughout. Attune did not commission, review or endorse it, and Programmable is not affiliated with Attune. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how Attune runs its business.

Something wrong, or do you represent Attune? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 308 ideas

    Fix the front doors: hurry's sign-up, one Attune home for bastion and akari, a contact route, the YC profile, llms.txt, the GitHub org page, fonts and share image, and a careers page.

  2. Days 31 to 609 ideas

    Turn shipping into attention: the nudge memory-layer post, release posts, the one-loop story, a runner-sizing table, an honest bastion comparison, design partners, hurry's Rust decision, akari share footers and nudge rule packs.

  3. Days 61 to 907 ideas

    Prove and monetise: a measured bastion recall benchmark and relaunch, hosted akari, a commercial licence, the agent-runs report, and the two wildcards.

The research behind the plan

3 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value drop-in tools that need no migration. The most cited problem: slow builds becoming the bottleneck once agents write code faster.

  • Open source and self-hosted, with no telemetry or lock-in
  • Agents forgetting project rules in long sessions
  • In their words: “faster builds, zero effort”

Market

Competitive landscape

4 competitors compared: CodeRabbit, Greptile, Depot and Blacksmith.

  • Gap to exploit: Review policy that is versioned in the repo and runs the same locally and in CI
  • CodeRabbit: Closed, hosted service; one reviewer per pull request rather than narrow, versioned gates
  • Greptile: Credit pricing per review; review policy lives in the vendor, not the repo

Hiring signals

Attune's one open role, a founding software engineer on YC's job board, is mostly Rust work and includes talking to customers.

  • Founding Software Engineer: Rust-heavy, customer-facing, still framed around build tools. Ideas 3, 16, 17, 19.

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks firstNew accounts get 100,000 free enrichment credits with code BETA100K (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammableMediaAn AI note taker, interpreter and webinar host for your calls (opens programmable.media in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence