Hivemind

Every day we run one project building in public through Hivemind, the strategy engine Myosin uses with clients.

Today: HerShape (hershape.app), an AI fitness app that adapts to your menstrual cycle.

Start with what is genuinely strong here, because there is a lot of it. The founder wrote the enemy down perfectly: "Every fitness app I looked at handed women the same plan every week, as if strength, recovery and appetite did not move across a menstrual cycle. They do." Your body copy is even better, "one body, four phases," "train with your body, not against it," "most apps hand every woman the same template." That is a real point of view, a real grievance, and a real, differentiated product underneath it. So this is not a positioning problem. It is a headline problem, and it is costing you the whole thing.

Look at the hero. The H1 is "AI fitness, built for women," and the cycle, the only idea that is actually yours, is demoted to the subhead. Count the words you spent. You led with "AI," and there are several hundred AI fitness apps, so that word does not separate you from anyone, and in a health context it can actively cost you trust, because "AI plan" reads to a skeptical woman as a generic template a robot spat out. Then you spent your second phrase on "built for women," which is the single most crowded claim in the entire fitness industry. Sweat says it. Kayla Itsines says it. Tone It Up says it. Every women's fitness brand on earth is built for women. It is table stakes, not a wedge. So your headline spends its two most valuable words putting you in the two most crowded rooms in fitness, and the one word that empties the room, cycle, is sitting downstairs.

The lens is own the enemy, and the enemy is the one-size-fits-all template, the plan handed to every woman as if her body were the same on day 3 and day 20. You named that enemy in your own bio and then walked past it in your headline. The fix is not more product. It is to lead with the fight you already picked. Three moves.

Move 1: Put the cycle and the grievance in the H1, and cut the two commodity words. Your best line is already written, it is just below the fold: "train with your body, not against it." Lead with that, or with the founder's version, "every plan you have ever followed ignored that your body changes across the month. This one is built around it." Then let "AI" live lower as the how, not the hook, because your buyer does not want AI, she wants to finally stop failing a plan that was never built for her. This week, swap the hero so the first thing a woman reads is the thing no competitor can say, not the two things all of them do.

Move 2: Answer the skeptic with evidence, because without it cycle-syncing reads as astrology. You already do the hard part, you name what changes in each phase, lower energy and iron needs while menstruating, rising strength into ovulation, rising appetite in the luteal phase. But you cite nothing, and your buyer has been burned by fitness pseudoscience her whole life, the detox teas and the waist trainers, so a claim without a reason lands in the same bucket. Add the why. A sentence of real physiology behind each phase, and a link to the research, turns "horoscope for workouts" into "informed coaching," and it does something bigger than convert, it builds the one moat you have. The AI is copyable, any app can bolt on a cycle input next quarter. Being the trusted authority on training a body that changes is not copyable, and evidence is how you earn that title.

Move 3: Position against the app she already has, not the fitness apps you keep comparing yourself to. Your real competitor is not Sweat. It is the period tracker already on her phone. Flo and Clue know exactly which phase she is in, and they do nothing with it. Her fitness app, meanwhile, acts every day and completely ignores the phase. You are the only thing that closes that gap, the one app that changes the workout because of the phase. So say it in exactly those terms: "Your tracker knows which phase you are in. Your fitness app ignores it. HerShape is the only one that trains you differently because of it." And use your depth as proof, the fact that you handle PCOS, endometriosis, postpartum, and perimenopause is evidence you were built cycle-first, not a generic app with a pink coat of paint and a toggle.

One risk worth naming, because it is the one that decides whether this is a company or a feature: the wedge is copyable on the surface. A large fitness app can add a "sync to your cycle" toggle, and a tracker like Flo can add workouts, and on the day either of them does, "adapts to your cycle" stops being unique. Your defense is to be the brand built entirely from the cycle out, identity, trust, evidence, and the depth to handle the conditions the giants will not touch, so that when a competitor bolts on a toggle, it is obviously a setting, and you are obviously the thing designed around her body. If cycle-syncing is a feature you own, you lose it the day someone bigger copies it. If it is your entire worldview, you keep the women who have felt unseen by every other app, and no toggle wins them back.

And the forcing question, the one to answer before you rewrite the hero: if a giant fitness app added a "sync to your cycle" toggle tomorrow, why would a woman still choose HerShape? If the honest answer is "because they bolted a setting onto a generic app, and HerShape was built to understand my body," then that identity, backed by evidence, is your entire company, and it belongs in the headline where "AI, built for women" is standing now. Answer it, and the strongest thing about you stops hiding under the most generic thing about you.

To HerShape: you did the hard part already. You found a real enemy, you built a real answer, and you wrote genuinely good copy about it. Now stop introducing yourself with the two words every competitor also uses. Lead with the cycle, prove it with physiology, and aim the whole story at the woman whose tracker knows her body and whose fitness app ignores it. You are the one that acts. Say that first.

Anyone else want their project run through the same lens? Reply with a link.

Every day we run one project building in public through Hivemind, the strategy engine Myosin uses with clients. Today: Operator (nowoperator.com), booking software for home service businesses.

Here is the strange thing about Operator: it has three different positionings, one for each place it describes itself, and they are at three completely different altitudes. On Indie Hackers the tagline is "growth platform for home service businesses." In the description the founder says the real reason it exists, "home service companies lose too many leads before they become booked jobs." And on the actual homepage the H1 is "Book more HVAC jobs with instant online estimates." Three surfaces, three products. The good news is that one of them is excellent. The bad news is that it is not the one on your brand.

Rank them, because the ranking is the whole strategy. "Growth platform for home service businesses" is the weakest sentence you have written. "Growth platform" is the emptiest phrase in B2B software, and "home service businesses" is the exact territory that ServiceTitan, Jobber, and Housecall Pro have spent a decade and a lot of money owning. When you say those words, you have walked into a knife fight against companies with sales teams, integrations, and a ten-year head start, and you have introduced yourself as a thinner version of them. Nobody switches their whole operation to a thinner ServiceTitan.

Now read your homepage H1 again: "Book more HVAC jobs with instant online estimates." That sentence is a completely different, much stronger company. It names one buyer, HVAC. It names the outcome, booked jobs. And it names a specific mechanism, instant online estimates, that the giant platforms are genuinely bad at. That is not a thinner ServiceTitan. That is a wedge ServiceTitan does not have. You already found your position. It is sitting on your own homepage while your brand points somewhere worse.

The lens is own the enemy, and the enemy is not ServiceTitan, and it is not the other booking tools. The enemy is the phone-tag quote. Here is how an HVAC lead actually dies. A homeowner's system breaks, they are hot or cold and a little panicked, and they do not want a relationship, they want a price. They fill out a form or leave a voicemail at three companies, and then they book whoever gives them a real number first. The company that makes them wait for a callback loses the job, every time, no matter how good they are. That waiting, that phone tag, is what kills the lead before it becomes a booked job, which is the exact thing your founder said Operator was built to stop. So build the whole story around killing it. Three moves.

Move 1: Pick one altitude and delete the other two. You cannot be a horizontal growth platform, a lead-recovery tool, and an HVAC instant-estimator at the same time, because each one tells a different buyer a different story and the sum is noise. The homepage already picked the winner. Make "book more HVAC jobs with instant online estimates" your only positioning, everywhere, and retire "growth platform for home service businesses" completely. This week, change the Indie Hackers tagline and every bio to match the homepage, so all three surfaces finally sell the same company.

Move 2: Lead with the estimator as the product, not as feature one of eight. Your homepage lists Instant Quotes, AI CSR, Online Booking, Website Chat, Speed to Lead, Follow-up Campaigns, Unified Inbox, and Performance Analytics. The moment a visitor sees eight features, they file you under "platform," and platforms get compared on breadth, and on breadth you lose to Housecall Pro. But seven of those eight things every competitor also has. The instant estimator, giving a homeowner a real repair range and replacement options right on the website without a callback, is the one thing they viscerally want and the incumbents mostly do not do. So make the estimator the entire hero. Let the AI CSR and the follow-up and the unified inbox be the quiet "and it handles the rest too" further down. Sell the one thing nobody else sells, not the seven things everybody sells.

Move 3: Put the enemy on the page in the homeowner's own words. Do not say "improve speed to lead," which is contractor jargon for a problem the contractor only half-believes they have. Say the thing that is actually happening to them: "Homeowners don't wait for a callback. They book whoever gives them a price first." That sentence makes an HVAC owner's stomach drop, because they have lost that job and they know it. Then the estimator is not a feature, it is the cure for a fear you just named. That is how you convert a skeptical contractor, by showing them the money they are already losing, not by listing what your software can do.

One risk worth naming, because it is the temptation that will pull you back toward the weak positioning: HVAC feels small, and the platform features work for plumbers, electricians, and roofers too, so it is tempting to say "home services" to look bigger, and there is even an agencies pricing tier hinting you are already eyeing the horizontal, white-label path. Resist it until the wedge is won. "Home service growth platform" is a graveyard fight against giants. "The instant estimator that wins HVAC jobs" is winnable, and every trade you named has the identical phone-tag problem, so once you own HVAC you expand to plumbing with a proven beachhead and a case study, not a broadside against ServiceTitan. Narrow is not smaller. Narrow is how you get a foothold big enough to go wide from.

And the forcing question, the one to answer before you change a word: if you had to delete every feature except one and every trade except one from the homepage, what survives? If the honest answer is the HVAC instant estimator, then that is your company, and "growth platform for home service businesses" is a slide for a future funding deck, not the first thing a contractor should read. Answer it, align all three surfaces behind it, and Operator stops being a thinner platform and starts being the only tool that wins the job before the competitor even calls back.

To Operator: you already did the hard part, you found the wedge and put it on your homepage. Now stop undercutting it. Kill "growth platform," lead with the estimator, and name the phone-tag quote as the enemy in the homeowner's own panic. Win HVAC first, and let the platform be the thing you grow into, not the thing you introduce yourself as.

Anyone else want their project run through the same lens? Reply with a link.

Every day we run one project building in public through Hivemind, the strategy engine Myosin uses with clients.

Today: Eider (eider.app), an expense splitter.

Start with the best sentence you have written about Eider, because it is not your headline. It is in your Indie Hackers description: "Sharing money with people you love should feel soft, not stressful. Every other splitter made it adversarial: approve this, dispute that, reject the other. Eider records, it doesn't enforce." That is a point of view. It takes a side. It is the reason someone would leave the app all their friends already use. And it is nowhere near the top of your page.

Look at what the page leads with instead. The H1 is "Shared expenses, all the way to settled." The Indie Hackers tagline is "the free, no-limits way to split expenses." Both are fighting on ground the incumbent already owns. "Settled" is the exact promise Splitwise makes, settle up, simplify the debts, net it down. When your headline restates the category's function, you are not a different product, you are a cleaner version of the same one, and nobody switches money apps for cleaner. "Free, no-limits" is worse, because it is a reaction to a competitor's paywall, which means your position is downstream of their pricing decision. If Splitwise drops its limits next quarter, your entire headline evaporates. And "free" on a money app quietly raises the question every user has learned to ask: if I am not paying, am I the product?

The lens is own the enemy, and the enemy is not Splitwise, and it is definitely not Splitwise's price. The enemy is adversarial money. Every expense splitter ever built is a tiny debt-collection system pointed at your friends: approve this charge, dispute that one, here is a reminder that Sarah owes you, settle up before you forget. The whole category treats the people you love like counterparties in a transaction. Your one real idea is to refuse that. "Eider records, it doesn't enforce" is not a feature, it is a worldview, and it is the only thing on your site that Splitwise cannot copy, because their entire architecture is enforcement. They cannot become soft without becoming a different company. Three moves.

Move 1: Put the feeling in the headline, and demote the function. The H1 should be the belief, something in the exact zone of "Eider records, it doesn't enforce" or "splitting money with people you love should never feel tense." Let "settled" and "netted down to the fewest payments" live below as proof that the soft thing also works. Let "free, no ads, no limits" be a line of reassurance, not the pitch. Landing pages fail when they explain the mechanism instead of selling the belief, and you have a genuine belief sitting in paragraph three. This week, swap your H1 for your Indie Hackers sentence and watch how differently the page reads.

Move 2: Name the enemy on the page, and show it. Do not just claim softness, contrast it. The other apps make you approve, dispute, reject, and nag. Eider just remembers, nets it down, and hands off to the payment app you already use, so nobody ever feels chased. Draw that contrast explicitly, because your buyer has felt the low-grade friction of being reminded that a friend owes them twelve dollars, and has felt weird being on the other end. Own the emotional category outright: the gentle way to share money among people who actually trust each other. That is a category of one, and the incumbent is structurally barred from entering it, because reminders and settle-up nagging are their core loop.

Move 3: Turn your two apparent weaknesses into the whole pitch, because both are actually strengths wearing the wrong label. The first is "free," which sounds like a discount and reads like a risk. You already have the answer: a Plus tier coming later, and Eider never holds or transfers money. Say that loudly. "We never touch your money and we will charge for advanced features later, not sell your data" is a trust asset, not fine print, and on a money app trust is the entire sale. The second is "it doesn't enforce," which sounds like a missing feature. Reframe it as a filter. Eider is built for the relationships where enforcement was never the point, couples, close friends, family, the roommate you actually like. If you need a collections system to get your money back from someone, you do not have an app problem, you have a relationship problem, and Eider is honest enough not to pretend otherwise. "It doesn't enforce" is how you select your true user instead of apologizing to the wrong one.

One risk worth naming, because it is the real tension in this wedge: softness narrows you. The moment you plant the flag in high-trust relationships, you walk away from the biggest, ugliest use case in the category, the roommate you barely know who owes you rent and will not pay. And you still face the most brutal force in this market, the network effect, because splitting needs both sides and everyone's friends are already on Splitwise. Here is why you take that trade anyway. "Free" will never pull a person off an app all their friends use, because the switching cost is social, not financial. A feeling might. The soft-money position is the only lever you have that is strong enough to justify the pain of switching, precisely because it is the one thing the incumbent cannot match without dismantling their own product. You do not out-network Splitwise. You make being on Splitwise feel slightly cold.

And the forcing question, the one to answer before you touch the page: if Splitwise dropped every limit and went completely free tomorrow, would anyone still switch to Eider? If your honest answer is no, then you are selling price, and you are one competitor decision away from having no pitch. If your answer is yes, because Splitwise still feels like a debt tracker and Eider feels like trust, then that feeling is your entire company, and it belongs in letters twice the size of the word "free." Answer that, and your homepage rewrites itself around the one thing nobody can take from you.

To Eider: you already wrote your headline, you just filed it under your bio and your third paragraph. The enemy is adversarial money, not Splitwise's price. Lead with the softness, name the debt-collector mindset you were built to refuse, and turn "free" and "doesn't enforce" from questions a visitor asks into the whole reason you exist. Say the true thing first.

Anyone else want their project run through the same lens? Reply with a link.

Every day we run one project building in public through Hivemind, the strategy engine Myosin uses with clients.

Today: Appaca (appaca.ai), an AI workspace for operators.

Start where the founder is strongest, because it is not on the homepage. In the Indie Hackers bio there is a real sentence with a real point of view: "I want us to be able to use software the way we work, not the way the software wants us to work." That is a belief. It takes a side. It is the reason someone would care. And it appears nowhere on the site that is supposed to sell the thing.

Now look at what the homepage actually leads with. The H1 is "AI workspace for operators," which is fine, and then the page opens up into everything. Build internal tools. Build AI agents. Store your knowledge. Connect Slack, Sheets, Airtable, Notion, HubSpot. Automate workflows. Approval flows, invoice processing, onboarding, contract tracking, vendor management, admin panels, custom CRMs, employee directories, SOP assistants, access reviews. Ten use cases in one breath. That is not a platform. It is a settings menu wearing a landing page.

The lens is own the enemy, and the enemy here is not Retool or Zapier or Notion. It is the feature list itself, the instinct to prove value by listing everything the product can do. Here is why that instinct is fatal for you specifically. The moment you say "internal tools builder," you are compared to Retool. The moment you say "AI agents," you are compared to every agent builder that launched this quarter. The moment you say "workspace," you are compared to Notion. You have volunteered for three fights at once, against three funded companies that each own their category, and you have picked all three on the same page. A visitor cannot tell what you are, so they file you under "another AI builder," and that folder is where products go to be forgotten.

There is a deeper problem underneath the crowding, and it is the one that decides your ceiling. You are sitting on the integration layer. Slack, Sheets, HubSpot, Notion. That layer is exactly what the big platforms absorb first. Assume Retool ships better AI tool-building, assume Notion ships agents, because they will, and they have the distribution and the capital to do it before you do. If your position is "we do what those platforms do, but together," the platforms simply do it together too, natively, next year. Being a thinner version of everyone is not a wedge. It is a countdown. Three moves.

Move 1: Take the side you already took. The founder's line, "software that works the way you work, not the way it wants you to," is the belief the whole page is missing, and belief is what converts a skeptical visitor, not a feature grid. Landing pages fail when they explain instead of convince. Put that conviction in the H1, cut the ten-use-case subhead to one, and let the features live lower on the page as proof that the belief is real. This week, rewrite the top of the site so a stranger knows what you stand against in the first sentence, not just what you can build.

Move 2: Pick one operator and own their entire job, instead of being a canvas for all ten. "AI workspace for operators" is still ten different people. Choose the single operator whose pain is sharpest and whose incumbent is weakest, and become the system that runs that job end to end. Picture the finance-ops person drowning in invoice approvals, vendor records, and contract renewals. Do not hand them a builder and a blank canvas. Hand them a finished thing that already runs their week. When you are "the way finance ops runs," you are not competing with Retool, because nobody shops for a generic builder when a product already does their exact job. A narrow wedge is a moat. A broad canvas is a feature the platform ships next quarter.

Move 3: Plan for the platform to ship your feature, and pre-build the part they will not. Natural-language app building is already being absorbed. The half a big platform cannot easily copy is the opinionated, pre-assembled workflow for one specific operator, plus the distribution into that operator's community. So stop shipping a builder and start shipping outcomes. Publish three finished operator apps, the invoice-approval system, the vendor tracker, the contract-renewal watcher, as things a buyer can use on day one without assembling anything. The builder becomes the engine underneath, not the pitch. Buyers pay for the job done, not for the tool that could, in theory, do it.

One risk worth naming, because it is the fear that keeps founders on the everything-page: narrowing feels like shrinking. You built a general platform, and choosing one operator feels like throwing away nine markets you already support. But look at the board honestly. A general platform with no free tier, competing against Retool, Notion, and Zapier on breadth, loses on brand, on funding, and on integrations, every single time. The narrow version competes with nobody, because it is the only thing built for that one operator's exact job, and once you own one operator you earn the right to the next. You are not deleting the nine use cases. You are refusing to lead with them.

And the forcing question, the one to answer before you touch a word of the page: if you had to delete every use case except one from the homepage, which operator's job would you keep? Whatever survives that cut is your company. The other nine are a settings menu, and a settings menu is not a story anyone repeats. Answer it, put that operator's belief in the headline, and the rest of the page finally has a spine.

To Appaca: you already wrote the winning sentence, you just put it in your bio instead of your headline. You do not need better positioning. You need to admit what you are actually building and take the side you clearly already believe in. Lead with the conviction, own one operator's whole job, and pre-build the outcome the platforms will not. Say one true thing, and stop being a thinner version of three companies at once.

Anyone else want their project run through the same lens? Reply with a link.

Every day we run one project building in public through Hivemind, the strategy engine Myosin uses with clients.

Today: eurobase (eurobase.app), an EU-sovereign Backend-as-a-Service pitched as the Supabase and Firebase alternative that keeps your data under European law.

Start with the good news, because there is real substance here. eurobase runs the same primitives a builder expects, Postgres, auth, storage, realtime, edge functions, on French infrastructure with no US jurisdiction, and the founder, Stefan, is explicit that the point was to do this without punishing anyone with worse developer experience. That last part matters more than he may realize, and I will come back to it. This is not vaporware wearing a flag. It is a real backend with a real reason to exist.

Now the hard part. "The sovereign Supabase alternative" felt like a category in 2024. In 2026 it is a shelf. Search for Supabase alternatives and you get an EU-only filter and a listicle with a dozen names, and every single one leads with the same sentence about data staying in Europe. When your primary differentiator is the exact thing twelve competitors also claim, it stops being a differentiator and becomes table stakes. Sovereignty gets you onto the shelf. It does not get you picked off it.

The lens is own the enemy, and the enemy is not Supabase. It is the sovereignty shelf, the growing rack of near-identical EU BaaS products all selling the same vibe. And here is what makes eurobase interesting: it is standing on that shelf holding two things almost nobody else has, and it has hidden both of them behind the generic pitch.

The first thing is an artifact instead of an argument. eurobase ships one-click GDPR Article 15 and 20 exports, the data-subject-access and portability requests, for every project. Stop and feel what that is. Every other product on the shelf is selling you a feeling of safety. eurobase is selling the actual document a Data Protection Officer needs to close a review. A developer does not migrate a live backend for a principle. A DPO signs off on a deliverable. You built the deliverable and then described it as a bullet point three scrolls down. That is the thing that ends a procurement conversation, and it belongs in the headline.

The second thing is a real vertical wedge, and it is currently in closed beta where nobody can see it. There is a Legal Team tier covering German legal retention requirements, BRAO, HGB, AO, GoBD, WORM storage. Read that list again, because it is the most valuable thing on your entire site. "Another EU alternative to Supabase" is a commodity. "The backend a regulated German law firm or financial practice can run without opening a compliance project" is a category of one. Nobody on the sovereignty shelf can follow you there without building specific legal-retention infrastructure, and most of them never will, because it is unglamorous and hard and requires actually understanding the regulations. That difficulty is not a cost. It is your moat. Three moves.

Move 1: Lead with the artifact you already shipped, not the adjective a dozen others share. The hero of the page should not be "sovereign." It should be the one-click DSAR export, framed as what it does, end your GDPR compliance review in an afternoon instead of a quarter. That is proof, and proof beats the promise every competitor on the shelf is making. This week, rewrite the top of the page around the export and demote the word "sovereign" to the supporting cast.

Move 2: Bring the Legal Team tier out of closed beta and make it the front door for the buyers who will actually pay. There are two eurobases fighting inside one homepage. One is a horizontal EU Supabase competing with a dozen lookalikes on price and vibe. The other is a vertical compliance backend for regulated German firms that competes with nobody, because nobody else built for BRAO and GoBD. The horizontal one is a feature war you will grind through forever. The vertical one is a wedge with real pricing power and a moat made of boring regulation. Point the site at the second business. A law firm or a fintech does not shop the Supabase-alternative shelf. They search for the one backend that keeps them compliant, and right now that backend exists and is invisible.

Move 3: Keep the promise the founder already named, because it is the reason this beats every fear-based pitch on the shelf. Stefan said the goal was to not punish users with worse developer experience, and that instinct is exactly right. Fear gets a builder to open the tab. Developer experience and a working migration path get them to actually switch. The single most valuable engineering effort is not another sovereignty argument, it is a one-command importer from Supabase and enough API compatibility that a team can point existing code at eurobase and have it run. When trying it costs an afternoon instead of a sprint, the artifact and the vertical finally have something to convert against. Put "migrate off Supabase in an afternoon" where the manifesto is now.

One risk worth naming, because it is the real strategic tension: breadth versus depth. The horizontal sovereign-BaaS play has a bigger apparent market but a crowded shelf and no moat. The German legal-tech vertical has a smaller market but pricing power, a defensible moat, and buyers who feel genuine pain. It is tempting to keep the broad pitch to look bigger and quietly run the vertical on the side. That is how you end up mediocre at both. The braver and, I think, correct move is to let the vertical lead and let the broad EU-BaaS crowd discover you underneath it, rather than the reverse.

And the forcing question, the one to answer before touching the homepage: if the US Cloud Act were repealed tomorrow and the sovereignty fear evaporated overnight, what is left? For most of the shelf, the honest answer is nothing, they were a headline. For eurobase the answer is unusually strong, because German retention law does not disappear with a data-transfer framework, and a DPO still needs that one-click export next quarter regardless of politics. That durable core, the compliance artifact and the regulated vertical, is your actual company. Sovereignty is just the reason someone gives it a first look. Lead with the part that survives the good news.

To eurobase: you already built the two things that win on this shelf, the document a DPO signs and a vertical nobody else can follow you into. You just hid them behind a word everyone else is using too. Put the export in the headline, bring the legal tier out of the dark, keep the developer experience you were right to protect, and let the sovereignty shelf keep selling a vibe you have already outgrown.

Anyone else want their project run through the same lens? Reply with a link.

Every day we run one project building in public through Hivemind, the strategy engine Myosin uses with clients.

Today: VCloud (varisymo.com), managed self-hosting for open-source apps.

Start with the sentence the founder wrote on Indie Hackers, because it is sharper than anything on the homepage: "running open source yourself is basically a second job." That is the whole business. VCloud is the company that takes the second job away. Nextcloud, GitLab, Rocket.Chat, all the tools a small team already wishes it could use, running for them with single sign-on, backups, and security patches handled, and nobody on the team ever paged at 2am. That is a real and valuable thing to sell.

Now look at what the homepage actually leads with: "Self-Hosted Applications Without the Complexity." The H1 opens with the two words that, to your buyer, mean the second job. An SMB with no IT team does not read "self-hosted" as freedom. They read it as the pager, the outage, the thing they pay SaaS to never think about. You spend the rest of the page walking back the promise your own headline made.

The lens is own the enemy, and the enemy here is not SaaS. It is the second job. This matters because your framing, "alternative to SaaS," picks a fight with the one thing your buyer actually likes. They did not choose Notion and Slack and GitHub because they love subscriptions. They chose them because those tools show up working and nobody has to run them. If you attack SaaS, you attack the convenience, and convenience is the exact thing you are selling. You are not the alternative to SaaS. You are SaaS economics for tools you get to own. Say that. Three moves.

Move 1: Rewrite the H1 as the outcome, not the architecture. "Self-Hosted Applications Without the Complexity" describes how the sausage is made. Your buyer wants the sausage. The headline should be the result they get to feel: your own GitLab, Nextcloud, and team chat, running for you, with no server to babysit and no per-seat bill that grows every time you hire. Put "self-hosted" lower on the page as the reason it is cheaper and yours, not as the first thing they see. This week, write three outcome-first headlines and test them against the current one.

Move 2: Aim the page at the buyer who signs the invoice, not the one who could set it up themselves. There are two people who might land here. One is a technical tinkerer who can already spin up a VPS and does not need you. The other is a founder or ops lead who is tired of renting eight tools, worried about where the data lives, and has no interest in touching a terminal. That second person is your customer, and they do not want to "self-host." They want to own their data and stop the subscription creep without hiring an admin. Name that dilemma in the hero. Once you speak to the buyer's problem instead of the builder's method, "self-hosted" stops being a warning label and becomes the proof that the promise is real.

Move 3: Pick the wedge before the platforms eat the easy half. One-click install of open-source apps is already commoditizing. Coolify does it, Railway and Render are close, and the OSS projects themselves keep shipping their own installers. If your pitch is "we make it one click," you are in a race you will lose to funded infrastructure companies. The half they will not touch is running it for a non-technical team as an ongoing service: the SSO nobody wants to configure, the backups nobody remembers to test, the patch that lands before the CVE does, and a human who owns uptime so the customer never learns what a reverse proxy is. That managed, we-own-the-outcome layer is your moat. Sell the babysitter, not the button, and price it like the second job you are absorbing, because that is what it is worth.

One risk worth naming, because it is the one that decides the ceiling: consumption pricing on compute invites a spreadsheet. A buyer who is comparing you to a SaaS subscription can also compare you to a raw VPS, and on pure compute the VPS wins every time. If the page frames the offer as cheap hosting, you lose to Hetzner. If it frames the offer as the second job removed, you are not selling CPU, you are selling the ops team they do not have to hire, and that is worth many times the compute. Guard the framing or the pricing will drag you into a commodity fight.

The forcing question, the one to answer before rewriting a line: if a buyer could keep only one of your two promises, "you own your data" or "you never touch a server again," which one closes the deal? One of those is a values pitch that a small slice of buyers cares about, and the other is a pain pitch that almost everyone with a growing tool bill feels. Whichever one closes, build the entire homepage around it, and let the other be the pleasant surprise on page two.

To VCloud: you already wrote the winning line, you just put it in an Indie Hackers post instead of your H1. The second job is the enemy. You are the company that takes it away. Lead with that, aim it at the person who signs, and own the managed layer the platforms will not touch.

Anyone else want their project run through the same lens? Reply with a link.

Every day we run one project building in public through Hivemind, the strategy engine Myosin uses with clients.

Today: Book Preflight (bookpreflight.com), a publishing product still on a waitlist.

Start with the insight, because it is genuinely good. You noticed that writing the manuscript is maybe thirty percent of the journey, and the other seventy percent, the positioning and audience and plan before the first word, and the publishing and launch and marketing after the last, is where a book lives or dies, and almost no tool helps with it. Writing apps stop at the draft. You picked up exactly where they quit. That is a real, ownable, unclaimed wedge, and most founders never find one that clean.

Here is the tension, and it is a packaging problem, not a product one. The person who needs you is a first-time author who is already overwhelmed and quietly afraid they will get this wrong. Your homepage meets them with "a twelve-phase, one-hundred-and-thirty-three-step publishing checklist." You built the aviation metaphor for a reason, a co-pilot, a flight plan, calm hands on the controls, and then the first thing the buyer sees is a number that means work. A co-pilot is relief. A hundred and thirty-three steps is homework. The figure you chose to signal thoroughness is the one most likely to make an overwhelmed author close the tab.

The lens is own the enemy, and the enemy is not Scrivener or any writing app. It is the lie that the manuscript is the finish line. Every writing tool, and every "write your book in thirty days" course, sells finishing the draft as the victory. It is not the victory, it is the starting line, and the moment an author types the final sentence and feels the floor drop out, because they suddenly have no idea how to publish, launch, or sell the thing, is the exact moment you exist for. Nobody is standing there when that happens. You can be. Three moves.

Move 1: Sell the relief, not the step count. A co-pilot never hands you a hundred and thirty-three tasks, it tells you the single next move. Lead with the feeling, something in the territory of "you finished the book. Now what?" and let the full checklist live one screen deeper, as reassuring proof that you have thought of everything, not as the headline that scares them off. This week, rewrite the hero so the felt complexity goes down when someone lands, not up, and put the phrase "the one next thing to do" near the top.

Move 2: Name the buyer, because "authors" is everyone and no one. The person who needs a publishing flight plan and will actually pay for it is the founder, the expert, the coach writing a nonfiction book to build authority or grow a business, not a hobbyist chasing a word count. Those two people want opposite things, and only one of them has a budget and a deadline. This week, rewrite the page for the authority-builder, say it plainly, "you wrote this book to grow your business, not to win a writing challenge," and add one qualifying question to the waitlist, "what is this book supposed to do for you," so you collect the people with a commercial reason and can talk to them like it.

Move 3: Make your own book the proof. You published a Stevie Award-winning book using this system, so the most persuasive marketing you own is the teardown of your own seventy percent, everything you did before the first word and after the last one that the writing tools never even mention. This week, write that as a post, not a feature list, the origin story of the plan, and let it carry the waitlist. It is proof no competitor can borrow, because they did not live it.

One honest risk, and it is the shadow side of your wedge: "everything before and after writing" is broad, and a product that promises the whole journey can read as doing everything and therefore nothing in particular. Breadth is hard to sell, because the buyer cannot picture the one moment they would reach for you. The hedge is to lead with a single, specific, painful moment, the finished-draft-now-what panic, own that one moment completely, and let the full depth reveal itself only after the author already trusts you with the first step. Sell the first step, deliver the whole flight.

And the forcing question, the one to answer before you build another phase: is your buyer paying to write a better book, or to make the book do something for them? Because if it is the second, and for the founder-author it always is, then you are not selling a publishing checklist, you are selling the authority, the leads, and the business the book is supposed to create. The checklist is the how. The outcome is the why. Sell the why, and the steps stop being a wall and start being the reason to trust you.

To Book Preflight: you found the part of the journey everyone else abandons, so do not describe it as a chore. Lead with the relief a co-pilot promises, point the whole thing at the author writing to build something, and let your own book be the proof that the seventy percent is where the win actually lives.

Anyone else want their project run through the same lens? Reply with a link.

Hivemind

Every day we run one project building in public through Hivemind, the strategy engine Myosin uses with clients.

Today: BrandGEO (brandgeo.co), an AI-visibility platform.

Start with the fire, because you are the only one in the category holding an extinguisher and you have it pointed at the floor. Every GEO tool right now tells a brand its house is on fire and then hands it a thermometer. Profound scores you, Peec scores you, Otterly scores you, and the market is drowning in visibility reports nobody acts on, because a score is not a plan. BrandGEO's actual product is the fix, the optimization plan for what to change, not just the number. That is the one thing the funded competitors do not have. And your homepage leads with the free audit anyway.

Here is the tension, and it is bigger than a hero headline. BrandGEO is two companies sharing one page. One sells a dashboard to brands who do not yet know they have a problem. The other sells a billable service to agencies who already know their clients do. Those are two different buyers, two different sales motions, and honestly two different years of a company's life, and running them side by side means each one is muffling the other.

The lens is own the enemy, and the enemy is not Vanta or Profound. It is scoreboard marketing: the quiet assumption that seeing the problem is the same as solving it. The whole category is building prettier thermometers and telling companies that a visibility score is a deliverable. It is not. The score is where the anxiety starts, not where the work ends. You are the one product built around the fix instead of the number, and you are hiding it. Three moves.

Move 1: Pick the agency, and pick it this week. A brand lands on the free audit, runs it, sees a number, and leaves, because it had no budget line for AI visibility before it arrived and a score does not create one. An agency principal reads "white-label this and bill your clients" and instantly sees a new service line. One of those buyers converts and one leaks. This week, give the agency the hero, the H1, and the first CTA, and move the free audit to a subpage or a subdomain like audit.brandgeo.co, where the direct traffic you already have can still land without eating your prime real estate.

Move 2: Name the category you are creating, not the one you are entering. "AI brand visibility" is already owned by five funded companies with more domain authority than you will build this year, and you cannot out-SEO them on their own term. But none of them are positioning as agency infrastructure. The category you can own outright is GEO-as-a-service for agencies. That reframing makes the funded competitors irrelevant to your buyer, because an agency does not shop brand-facing dashboards, and it hands agencies language they can repeat to their own clients. This week, rewrite the hero for the agency's growth problem, something in the zone of "your clients do not know AI is misrepresenting them, you can fix it and bill for it," and test it on five agency operators you respect. If they do not immediately ask how to sign up, it is not sharp enough yet.

Move 3: Ship a reseller playbook, not a product page. An agency does not need another tool, it needs a deliverable it can mark up and a script to sell it. The white-label PDF is the product, but the sale is the playbook: how to pitch the audit to a client, what to charge, and how to turn the optimization plan into an ongoing retainer instead of a one-time report. This week, write a one-page "How to sell AI visibility audits to your clients," include a sample client email and a follow-up script for presenting the findings, and gate it behind an email. That document, not the free audit, is your real top of funnel, because it collects the exact people who can resell you.

One honest risk, and it is the one that decides whether this wedge is a business: agencies move slow and hate learning new tools. The clean white-label pitch will get a lot of nods and very few first audits, because the agency principal agrees in the meeting and then never logs in. The hedge is to remove the first step entirely: run their first three audits for them, on their branding, and hand them client-ready reports before they ever touch the product. Make the cost of starting zero. Once an agency's own clients have seen a report with that agency's name on it, the agency is not evaluating you anymore, it is locked in, because switching means explaining to clients why the reports suddenly look different.

And the forcing question, the one to answer before you rewrite a word: if you had to delete one of your two offerings today, the brand dashboard or the agency service, and you could not bring it back for six months, which one survives? Whichever you cannot live without is your company. The other one is a distraction wearing the costume of a second income stream. Answer that honestly, and the entire homepage writes itself.

To BrandGEO: the category is selling thermometers and you built the extinguisher, so stop apologizing for it on a shared page. Point the whole product at the agencies who already feel the heat, give them a deliverable and a script to resell it, and let the funded competitors keep scoring a fire they cannot put out.

Anyone else want their project run through the same lens? Reply with a link.

Every day we run one project building in public through Hivemind, the strategy engine Myosin uses with clients. Today: Adwave (adwave.com), a platform that turns your website into live ad campaigns.

Start with the thing you do that almost nobody else can, because it is buried on your own page. Adwave lets a local business run a real streaming-TV ad in minutes, from nothing but its website URL. That is remarkable. Television has spent decades locked behind upfront negotiations, six-figure minimums, agency retainers, and media buyers, and you handed a neighborhood gym the ability to air a TV ad tonight. Then your homepage opens with "from your website to live ad campaigns on TV, Google, and Meta in minutes," which lists all three channels as equals and files you next to every AI ad-creative tool on the market.

Here is the tension in one sentence: the one thing nobody else can do is hidden behind the one thing everyone can do. Self-serve streaming TV for the small business is a category nobody owns. AI-generated Google and Meta ads are a commodity with a thousand sellers. By putting them side by side in your headline, you spend your scarcest asset, distinctiveness, to buy a seat in the most crowded room in software.

The lens is own the enemy, and the enemy is not AdCreative or Meta's own ad tools. It is the idea that TV was built to exclude you: the whole legacy stack of minimums and gatekeepers that told every small business owner, for decades, that television was not for them. That message got so deep that most owners never even considered TV, they do not know they were locked out, because nobody ever told them there was a door. Your tribe is the local business that has always been told to "just run some Facebook ads." Your prophecy is that the line between small-business marketing and real advertising is gone, and it is not coming back. Your job is to make that wall visible and hand people a sledgehammer. Three moves.

Move 1: Rewrite the homepage around one claim. "On TV, Google, and Meta" turns your miracle into a feature list. Strip Google and Meta out of the hero and lead with the transformation only you deliver, something in the territory of "Your website. A real TV ad. Running tonight." Google and Meta drop to a single line further down, "plus Google, Meta, and the web," the bonus, not the pitch. This week, draft three hero versions and run each through one test: write the headline a journalist would publish about Adwave, and if that headline mentions Google or Meta, the positioning is still wrong.

Move 2: Kill the dual name. Adwave is the company, Waverunner is the product, and the two of them split every referral, every search query, every word-of-mouth mention, and every piece of press. Two names is not a naming strategy, it is a leak. This week, make the call, pick one, and consolidate every touchpoint behind it: homepage, meta titles, ad accounts, social handles, the deck. A young brand cannot afford to build awareness for two things that mean the same thing.

Move 3: Get five local businesses live on streaming TV and make that your entire marketing engine. The proof is not a demo reel, it is a real HVAC company, a neighborhood restaurant, a boutique gym, each with a real ad running on real streaming inventory, and their reaction on film. That content sells the impossible thing better than any feature list. This week, find five existing users willing to go live at little or no cost, offer to cover the first bit of media spend in exchange for a filmed case study, and set one goal: five live streaming-TV ads from five different local businesses inside thirty days.

One honest risk, and it is the one that sets your clock: if streaming inventory becomes a commodity and Google or Meta ship self-serve TV placements inside their own platforms, your wedge collapses from a moat into a feature. Meta is already testing connected-TV placements, and Google owns YouTube, so the window to own this position is real but not permanent. The hedge is that your defensibility was never the inventory, it is the workflow and the association: URL to a live multi-channel campaign in minutes, with TV as the anchor. If "Adwave means TV ads for small business" is planted in enough heads before the giants arrive, you keep the category mental real estate even after they enter. Speed is the hedge, and every month spent buried inside a three-channel commodity pitch is a month the window closes.

And the forcing question, the one to answer before you rewrite a word: is streaming TV actually what your customers ask for, or is it just what makes you sound different in a pitch deck? If your users would trade the TV placement for a higher-performing Meta ad set, then leading with TV is a positioning move that fights your own demand, and you need to know that first. Ask ten customers which channel they would keep if they could keep only one. Their answer decides the whole page.

To Adwave: you built a door in a wall that has stood for fifty years, and then you described it as one of three doors, two of which everyone already has. Lead with the one only you can open. Put the small business on television, make that your whole first screen, and let Google and Meta be the pleasant footnote underneath the thing that actually stops people cold.

Anyone else want their project run through the same lens? Reply with a link.

Every day we run one project building in public through Hivemind, the strategy engine Myosin uses with clients.

Today: SpamCipher (spamcipher.com), a cold email platform.

Start with the sentence you wrote on Indie Hackers, because it is a sharper company than your homepage. You said the cold email deliverability loop is broken: you only get data on a failed campaign after it has already failed, once the damage is done. That is a real, specific, and almost unclaimed insight. Then your homepage opens with "cold email platform for unlimited, automated sending" and "run cold email at scale," which is the exact lane Instantly, Smartlead, and Lemlist already own, and where a newer name gets lost.

Here is the tension, and it is sharper than a positioning miss. Your defensible product is predictive deliverability, knowing you will land in the inbox before you hit send. But your homepage sells unlimited blasting at scale, which is the precise behavior that destroys deliverability. You are marketing the disease and burying the cure. A careful sender, the person who would actually pay to protect a domain, reads "unlimited sending at scale" and hears the thing that got them into trouble in the first place.

The lens is own the enemy, and the enemy is not Instantly or Smartlead. It is send-and-pray email: the broken loop the whole industry runs on. Blast thousands of emails, wait three days, discover your domain reputation is torched, repeat. You learn you failed after the failure is irreversible. Every tool out there optimizes the blast. Nobody owns the moment before you hit send, when the choice to protect the domain or burn it still exists. That moment is yours to own. Three moves.

Move 1: Rewrite the hero around the wedge, not the commodity. "Unlimited automated sending" is a feature, and it is the wrong one. The outcome is knowing your email lands before you send it. You already wrote the line on Indie Hackers. This week, replace the hero with one version of it, something like "Stop finding out you landed in spam after it is too late," give it one CTA, and cut "unlimited sending at scale" out of the hero entirely. If it survives at all, it survives far down the page.

Move 2: Rebuild the page as problem, agitation, solution, using the real pain. Right now the page skips the problem and jumps to features, so the visitor never feels the thing you are curing. Name it with specificity instead: you sent five thousand emails on Tuesday, forty percent hit spam by Thursday, and you found out Monday from a prospect who mentioned it, and now your domain needs six weeks to recover. Then the solve: SpamCipher scores your deliverability risk before you send, on your own domains, so you protect reputation instead of repairing it. This week, write that problem section as a story, not a feature list. That story is the page.

Move 3: Turn your signup into a filter, not a net. You do not want everyone who wants to blast, you want the people who have already burned a domain and felt the pain. This week, add one qualifying question to the signup, "how many domains have you burned running cold outreach?" The people who answer two or more are your ICP, they feel the wedge instantly, and they are also your best case studies for the deliverability claim. Everyone else is a tire-kicker who will churn. Give the burned cohort early access and a personal note from you.

One honest risk, and it is the one to plan for now: the wedge may not stay defensible. A pre-send inbox-placement checker is a better story than "blast unlimited," but if that is all it is, Instantly or Smartlead can ship their own version in a single sprint, and "we did it first" is not a moat. The hedge is to move while the incumbents are still selling scale, and to build a public deliverability score that becomes the number people quote, the way PageSpeed Insights became the standard for site speed. If the SpamCipher score is what founders cite when they talk about cold email health, you own the category, and the moat is the benchmark, not the feature.

And the forcing question, because you already know the answer: you wrote the sharp version of this product on Indie Hackers, and the homepage says something else entirely. Which one are you actually building toward, and who told you "unlimited sending at scale" belonged at the top of a deliverability company's page?

To SpamCipher: your name is about getting into the inbox, and your homepage is about getting out as many emails as possible. Those are opposite promises. Lead with the one only you are making, that a sender can know before they send, own the moment before the blast, and let the scale live quietly underneath, where it cannot undermine the very thing you exist to protect.

Anyone else want their project run through the same lens? Reply with a link.