Website Changes at AI Speed. Under Your Control.

Maintain and optimize your website after launch. Requests, AI execution, team governance, and your CMS, connected in one system.

Website work breaks in two places.

Requests live everywhere except where work happens

Slack threads, email chains, spreadsheet rows, group chats. Every channel generates website work. None of them track whether it actually ships.

Changes go live with no record

The pricing page changed last Tuesday. Who pushed it? What did it replace? Was it approved? The only audit trail is someone's memory.

Your website creates constant work. Small tasks that never stop accumulating.

Updates, content edits, copy fixes, reviews, approvals, CMS changes, optimizations. None of them are hard. All of them need doing. The gap between what arrives and what ships is where teams quietly fall behind.

Built for

Teams That Ship More Than They Staff

Five people requesting changes, one person making them. The backlog fills up before anyone notices.

Websites With Hundreds of Pages

Content drifts out of date faster than anyone can review. Pages go stale without warning.

Sites Where the Website Is the Pipeline

When the site drives revenue, a bad change costs real money. Every edit needs a reason before it ships.

One System, From the Ask to the Published Change.

Most tools stop at a recommendation. The rest stop at a ticket. Declunk connects the two.

1

Analysis

Decides what should change, and why.

2

Requests

Carries the work, with an owner and an approver.

3

Execution

Makes the change in your CMS.

AI does the heavy work. Your team makes the decisions.

Follow One Request All the Way Through.

1

Someone Asks

A request lands on the board, tied to a real site and a real page. Not a message in a channel that someone has to remember.

2

Someone Owns It

An owner and an approver, before any work starts.

3

AI Proposes

You see the change it wants to make and the reasoning behind it, before anything moves.

4

You Approve, and It Ships

The change lands in Webflow. The record shows what changed, who asked for it, who approved it, and why.

Live today, on real sites, every day.

AI Does Not Touch Your Website Until You Say So.

The AI proposes a plan. You approve it, and it implements only what you approved. On enterprise setups, work occurs on a Webflow branch, keeping it from your live site.

Connects to the Tools You Already Use

Your CMS, your AI, your SEO stack. Declunk plugs into all of them so everything works together in one place.

The Same Rails, Pointed at Getting Found.

Business
Content
Company Website
Main Services
Service Areas
Commerce Model
Goals
Personas
Niches

Being recommended by AI search is one of the jobs a website now has. Declunk starts from a complete picture of your business rather than a scan of your pages, then tells you what to change and why.

More on AEO

Three Things People Ask.

Webflow already does some of this.
It does, on their top plan tier. Below that, their agents are not available at all. And their recommendations are accepted or dismissed, with no owner, no approver, and no record of why.
Our agency already does this with AI agents.
Then their agents decide and their log holds the history. Here your team approves every change, and the record stays on your side no matter who does the work.
This is a ticket system.
It has one, and that is not why anyone buys it. A ticket in a general tool is a note. A request here is tied to a live page and ends in a published change.

What Is Live, and What Is Not.

Now
  • Requests tied to live sites and pages
  • Activity ledger
  • Webflow site and page sync
  • Publish and approval history
Next
  • AI execution end to end
  • AEO
  • Workflows
Later
  • SEO and CRO
  • More CMS connectors
  • Reporting across sites

We ship incrementally and update this page as we go.

Answers

What is Declunk?
A platform for maintaining and optimizing a website after it goes live. Requests come in from anyone on the team, AI proposes each change with its reasoning, a person approves it, and it publishes to the CMS with a record of what changed and why.
Who is it for?
Teams responsible for a website that generates continuous work: many stakeholders sending requests, a large content footprint, or a site that carries demand generation. It is not defined by how many sites you run.
What does it replace?
The gap between a project management tool and the CMS. Today that gap is filled by spreadsheets, chat messages and developer time.
How is it different?
A content decision arrives with its reasoning, routed as a request with a named owner and approver, published with a record of why, on your side. Other tools do one or two of those. None do all three.
What is live today?
Request management, Webflow site and page sync, and publish and approval history. AI execution and AEO analysis are in build.

Get Early Access.

We are opening Declunk to a small group first. Tell us about your site and we will be in touch.

No spam. Unsubscribe anytime.