From a URL to a shipped change — with proof it worked
Bladesmith is not a chat window that gives advice. It is a loop that runs on your product every day, proposes specific work with the evidence behind it, executes what you approve, and measures what changed.
The loop
Seven steps, on repeat
The channel changes. The discipline does not.
- 01
Signal
A number moves in your analytics — or stops moving.
- 02
Diagnosis
It reads the funnel, the site and the code to work out why.
- 03
Proposal
A specific action, with the evidence, the expected effect and the cost.
- 04
Approval
You approve in one click. Nothing happens before that.
- 05
Execution
A pull request, a send, a write to a connected tool — whichever route is available.
- 06
Outcome
The metric is measured after the fact and attached to the action that caused it.
- 07
Learning
The result updates what we recommend next — for you, and for products like yours.
Your first week
Six states, each with exactly one thing to do
The product only ever shows you what is already true, and frames the next step as a promise. You are never handed a menu of ten things and left to guess.
- S0A draft GTM plan
Paste your product URL
Bladesmith reads your site and returns positioning, ICP, prioritized channels and quick wins — before you sign up, in about a minute.
- S1A ratified plan
Confirm the foundation
Three questions: who it is for, how you sound, what this quarter has to achieve. Your answers override anything we inferred — you are the authority on your own product.
- S2A north-star baseline
Give it eyes
Connect GA4, PostHog or Search Console. No analytics at all? The first pull request is the instrumentation: acquisition, activation, conversion, wired to your funnel.
- S3Ready assets, first queued actions
Run the first plays
Generate the Growth Kit — the assets, the target communities, the keyword map, the launch material — and send the first items to your inbox.
- S4The daily habit
Ten minutes a day
The GTM Inbox becomes home. Each item is a signal, a diagnosis, and a proposal with its route and cost. You approve, edit or dismiss.
- S5Compounding
Watch it learn
Outcomes come back and attach themselves to the actions that caused them. Channel priors update. What worked gets proposed again, sharper.
Execution routes
Every action declares how it can be done
What to do is stated in plain marketing terms — publish the comparison page, fix this CTA, launch the survey. How it gets done is resolved at run time from whatever you have connected, and Bladesmith always takes the highest rung available.
A pull request
Landing page, pricing copy, onboarding, structured data, instrumentation. The change arrives as a diff you review, merge and can revert.
A connected tool
Your email provider, your analytics, your CMS. Bladesmith writes through the integration you already own, with your keys.
A configuration change
A feature flag, an experiment, a survey — shipped as a payload to the tool that runs it.
The finished asset
Where no safe automated route exists, you get the completed work and a two-minute instruction. Always available, never a dead end.
The rule is that it never blocks — it degrades. Which is also why the free tier is a real product: rung zero is always available.
The consent mechanism
We don't ask for trust. We ask for a review.
Granting an agent write access to your product should be a rational decision, not a leap of faith. A pull request makes it one: it is a proposal, it is diffable, a human approves it, it is auditable, and it is revertible.
export default function Pricing() {return (- <section className="pt-24">- <PlanGrid plans={plans} />+ <section className="pt-12">+ <SignupCta id="start" variant="primary" />+ <PlanGrid plans={plans} compareAnchor /></section>
Nothing executes without approval
Every action stops at your inbox. Approving is one click; so is dismissing.
Every action is reversible
In the repo that means a revert. Elsewhere it means we tell you exactly what was done, where, and when.
Your keys stay yours
Connections are yours and revocable. Bladesmith acts through them, and stops the moment you disconnect.
It degrades, it does not bluff
When a channel cannot be executed safely, the agent says so and hands you the asset. It never pretends to have shipped.
The part nobody else does
Then it goes back and checks
After an action ships, Bladesmith watches the metric it was meant to move, over the window where an effect would show, and attaches the answer to the action that caused it. That record is what makes the next recommendation better than the last one — for you, and for the next founder whose product looks like yours.
An action whose outcome we cannot observe has not been executed. It has been performed.
Start with the plan. Decide about the rest later.
The analysis, the plan and the assets cost nothing and need no repository. Connect more when you want the agents to do the work rather than describe it.
Connect GitHub insteadFree tier · no credit card · nothing is sent, posted or shipped without your approval