Coming soon

Every change,
under control.

From the first request to the final sign-off, the cost agreed and the work accepted, ChangeControl keeps the whole of a change in one place, with a clear record the entire way through.

One message when it opens. No noise, no spam.
You are on the list. We will be in touch the day it opens.
CR-2294
Update checkout copy and pricing table
Raised by the requester, assigned to the team
Submitted
Review
Approved
In progress
Closed
09:12Opened by the requester
09:34Reviewed and approved
10:02Moved to in progress
Internal noteShared comment

A new product from Axenara, built to fit the way you already work.

The problem

Change usually lives
everywhere except one place.

A request starts in an email, gets argued out in chat, the cost is agreed on a call, and the sign-off happens somewhere none of them can see. By the time anyone asks what was agreed, the answer has to be pieced back together. ChangeControl exists to end that.

Scattered

The ask, the discussion, the quote and the sign-off all sit in different tools, so the full picture never lives in one spot.

Stalled

Requests wait in inboxes with no clear owner and no clear next step, and the people waiting cannot tell where things stand.

Unrecorded

When a decision is questioned later, there is no single record of who asked, who agreed and what actually changed.

What is inside

The whole of a change,
one system at a time.

ChangeControl carries a change from request to done. Each part below is built in, and they share the same record so nothing falls between them.

Change requests

Every request in one queue

The heart of it. Anyone raises a request, on either side, using a form that suits the kind of change it is. Everything that follows hangs off that one record.

  • Request types and forms shaped to your work
  • Clear owner and status on every one
  • One place both sides can see
Requests
Open requestsNew request
AL
Update checkout copy and pricing table
Content change
In review
RW
Add a delivery note field at checkout
Feature
Submitted
TM
Revise the returns policy page
Content change
Approved
AL
Fix VAT line on invoices
Fix
On hold
Sign-off

Approvals that actually gate the work

Sign-off is a real step, not a polite note in a thread. Send a change to the people who decide, one after another or together, and it only moves once they have all said go.

  • One or several approvers per change
  • Request changes back without losing the thread
  • Who signed, and when, kept on the record
Sign-off
Approve: update checkout copy
Needs sign-off from two people
1 of 2 approved
RWReviewerApproved
TMApproverPending
ApproveRequest changes
Acceptance testing

Checked and accepted before it ships

When work is ready, it goes to acceptance. The people who asked run through what was promised, mark off what passes, flag what does not, and the change cannot be accepted until it all holds.

  • A clear checklist drawn from the request
  • Flag what needs work and send it back
  • Acceptance recorded against the change
Acceptance
User acceptance2 of 3 passed
Checkout total updates correctlyPass
Mobile layout holds togetherPass
Discount code applies on second itemNeeds work
1 item to resolve before acceptAccept
Quotes, agreements and billing

When a change has a cost, settle it here too

Some changes come with a price. Quote it on the request, let the other side accept it, capture the agreement, and have it ready to bill, without leaving the change or hunting for what was agreed.

  • Quote a change in a few lines
  • Accepted quotes become the agreement
  • Built in to start, with room to grow
Quote
Quote for CR-2294Sent
Design changes£320
Build and test£540
Content update£140
Total£0
Agreement readyAccept quote
And throughout

The parts that tie it together.

Underneath every system above, the same handful of things are always true.

Both sides, one room

Made for any two sides, whoever asks and whoever decides. Each side gets its own view of the same change.

A flow you shape

Switch on the stages you use and set up the request types you need, so the flow forms around your process.

Talk in the open or aside

Internal notes stay with your team. Shared comments go to the other side. Both sit next to the change.

A clear view for clients

The people you work with see what they need and nothing they should not, and they never have to chase you.

A full record

Who asked, who approved, what was agreed and what changed, kept in order on every request.

Grows with you

Turn on the parts you need now and add more as you go. It starts simple and never makes you start over.

How it works

From asked to done,
in clear steps.

Every change follows the same simple shape, so anyone can tell where a thing stands at a glance.

01

Raise

Someone opens a request, on either side, using a form that fits the kind of change it is.

02

Agree

It is reviewed, quoted if there is a cost, and signed off. The change only moves once it is agreed.

03

Build

The work happens, with notes and context staying attached to the same record throughout.

04

Accept

The other side checks it against what was promised, accepts it, and the history stays for good.

The lifecycle
Draft Submitted In progress Closed

Four stages ship as standard. When you need more nuance you can switch on extra ones, such as under review, awaiting info, awaiting approval, ready for sign-off and on hold, and the flow grows to match.

Who it is for

Wherever a request
needs a yes.

ChangeControl is not tied to one industry or one direction. If one group asks and another decides, it fits.

Studios and agencies

Work with clients in the open

Clients raise changes, agree the cost and sign off in one place, so scope stays clear and nothing is a lost email.

Teams and suppliers

Keep both sides aligned

Requests run between you and the people you depend on, with a shared record everyone can point to.

Internal teams

Make change accountable

When a change needs a decision before it happens, it follows the same clear route every single time.

Part of the Axenara family

Made by Axenara.

Axenara is a web and software studio. We take the awkward, technical parts of being online off people's hands, building and looking after the things businesses run on, and we make our own products to do that job better. ChangeControl is one of them.

It is built on the same foundations as everything else we make, so it is steady, considered and quietly reliable. That is the whole idea.

Visit axenara.com
Questions

The short answers.

It is one place to raise change requests, agree them, do the work and have it accepted, with the full history kept on every request. Think of it as the route a change takes, from the first ask to the final sign-off.
Change requests, sign-off and approvals, acceptance testing, and quoting, agreements and billing for the changes that carry a cost. They are built in and share the same record, so a change does not jump between tools as it moves along.
No. It is built to work between any two sides, whoever asks and whoever decides. A studio and its clients, a team and its suppliers, or a group inside one business all fit the same way.
No. You choose the stages and request types that match how you work, and the flow forms around that. It is meant to be set up by the people who run the process, not handed to a developer.
Yes. The other side gets a clear view of what they need to see, where they can raise requests, agree quotes, follow progress and sign off, without seeing your internal notes.
Each request carries its own history in order, showing who asked, who approved, what was agreed and what changed. There is no separate log to manage, it is simply part of every request.
We are building it now. Join the list and we will email you the day it opens. That is the only message you will get from us until then.
Get on the list

Be there when it opens.

ChangeControl is on its way. Leave your email and we will tell you the day you can start using it.

One message when it opens. Nothing else.
You are on the list. We will be in touch the day it opens.