Equality Action Plan Builder
Plan gender pay gap and menopause actions the way GOV.UK asks
What is Equality Action Plan Builder?
Equality Action Plan Builder is for UK employers with 250 or more staff who will have to publish an action plan alongside their gender pay gap figures. The government says this becomes mandatory from spring 2027, subject to secondary legislation, and its guidance lists 18 actions in five groups.
You tick the actions you will take and mark each one as new or in progress, or already embedded. The builder checks the three published minimums as you go (at least one gender pay gap action, at least one menopause action and at least two actions that are new or in progress), counts words against the 100 and 200 word limits, warns about links in the text, and turns your published pay gap figures into a short diagnosis. The plan comes out as text in the order the guidance sets out.
The builder is free and nothing leaves your browser. Pro is 79 USD once per organisation for the analysis of your HR export, a sign-off pack PDF, a plan page for your website, a measures tracker and a staff consultation kit.
Ready to launch?
Submit your product and get discovered by builders and creators worldwide.
Launch Now
FounderPlaybooks.
What other founders did to grow.
2722 dispatches from hundreds of founders, pulled from the week's best podcasts.
Repeat purchase mechanics are great for that consumable transaction that you want users to do so it is a little harder when you're trying to offer like here's this paintbrush for a lifetime then you don't have much left to offer and so you're kind of limiting the use there.
Repeat-Purchase Mechanics Make Consumables Work — Avoid the Lifetime Item Trap
Consumables generate LTV through repetition, not one-time purchase — that's the entire mechanism. Selling a feature 'for life' destroys the monetization loop because there's nothing left to sell. The dating-app model (boosts that expire, flowers that get spent) is the archetype: each use is inherently temporary, naturally driving repeat purchase without feeling coercive.
The biggest mistake in web2app is treating it as a binary. Web2app versus app install is not the question. The question is: where is this user coming from and what context are they in? Match the journey to that context. Sometimes that means web. Sometimes that means the App Store.
Context of the ad placement matters more than web vs app choice — match the journey to traffic source
Petit's framework is traffic-source-first: Facebook and Google search users may convert fine through direct app install because they're in high-intent, familiar territory. TikTok users, Outbrain users, or cold display traffic are in lower-intent, lower-trust contexts where a landing page warms them before asking for an app install. The web landing page's job is context bridging, not fee avoidance.
There's a play for whatever you're stuck on.
Read all 2722 playbooks