AWRA OpsHub Search

I Need This, Commission It

Every post on this site ends with a list of things we can add to your workspace. Each item on that list now has two buttons under it — one to say you need it, one to ask us to build it for you — and what you press decides what we build next.

Operations Metrics Washingtone Aura 6 min read

Scroll to the bottom of almost any page on this site and you will find a three-column ledger. The first column is what is built. The third is where we point you to a specialist. The middle one, under a wrench, is More we can add to your workspace: capabilities a customer can commission. Until this month that column was a list you could read and then email us about. Now every item in it is a button.

Why the middle column exists

Software websites usually describe the product as finished and leave the buyer to find the edges during implementation. We decided some time ago to publish the edges instead, and to write them as offers rather than confessions, because almost everything on that list is a few days or weeks of work we would happily do for a customer who needs it. Some posts are a single offer from start to finish, such as dependency types for the critical path. A list of offers is only useful, though, if the people reading it can answer it.

Two buttons under every offer

I need this is a vote. It needs no account, no email and no form. Press it and it says “Noted, thank you”. Commission it opens a short form for an organisation that wants the capability built for its own workspace: your name, a work email, your organisation, optionally your country and what you need it to do. That is a sales conversation, and it is treated as one.

I need this

  • Anonymous, one press
  • One vote per offer per visitor
  • Counts towards what we build next
  • Nothing to fill in

Commission it

  • Name, work email and organisation
  • Comes straight to the founder as a request
  • Weighs five votes in the ranking
  • An email to you when it ships

How a vote is counted, and what is not kept

A vote is anonymous on purpose, and counting anonymous votes honestly takes a little care. Your browser gets a random identifier the first time you vote; we store only a keyed hash of it, never the identifier itself, so the database cannot be used to recognise you. We also keep a keyed hash of your IP address, and for 24 hours a second vote on the same offer from the same address is not counted. Automated submissions are answered exactly as a person would be, and not counted.

The pages carrying ledgers are cached and served to every visitor alike, so the button itself carries nothing about you. Whether you have already pressed it is remembered in your own browser. The running counts are shown on the roadmap, under Most requested right now, ranked so that one commission request weighs the same as five votes.

A vote tells us an offer matters. A commission tells us who it matters to, and we can build it for them.

Where the offers come from

The catalogue of offers is read from every ledger on the public site: the middle column of every blog post, the We can add rows in a post’s capability stack (the integration roadmap has several), every landing page and role page that carries a ledger, and the ledgers written into the feature pages. Rebuilding it never resets a vote, a request or a status. And if a page’s ledger cannot be read, the rebuild fails loudly rather than skipping it, because a skipped page would print buttons that lead nowhere.

What happens on our side

  1. Ranked

    Every offer is listed by votes and commission requests, with the requests themselves beside it.

  2. Given a status

    Open, planned, building or shipped, with a note, so the roadmap shows what is moving.

  3. Built

    For the organisation that commissioned it, in their workspace, on a written scope.

  4. Announced to the people who asked

    Marking an offer shipped can email each person who commissioned it, once, about the one thing they asked for.

That shipped email is a reply to your own request, not a newsletter: it goes to the address you typed on the form about the capability you named, and never twice. The monthly email is a separate box on the form, unticked, and commissioning something does not add you to it. To see what the ranking looks like at the moment, the roadmap is rendered fresh on each visit.

Try it here

This post has a ledger of its own at the bottom, like every other. Its middle column carries the same two buttons, so if you would use one of the extensions to this feature, the button is a scroll away.

More we can add

More ways to tell us what to build

Votes, commission requests, the ranking on the roadmap and the shipped email are in place. These are the next steps for the loop itself.

An offer’s status on the ledger itself

Planned or building shown under the item on the page where you found it, not only on the roadmap.

Updates for voters who want them

An optional address under the vote, for a single email when the offer ships.

Shared commissions

Several organisations commissioning the same item, with the scope and cost shared between them.

The straight answer

What AWRA OpsHub does today

  • I need this under every offer in every public ledger: anonymous, one per visitor, counted with hashed identifiers.
  • Commission it, a short form that reaches the founder as a request and weighs five votes.
  • A catalogue of offers rebuilt from every blog post, landing page, role page and feature page ledger.
  • Most requested right now on the roadmap, ranked from votes and commissions.
  • Statuses and a shipped email to each person who commissioned an offer, sent once.

More we can add to your workspace

  • An offer’s status shown on the ledger where it appears. Commission it
  • An optional email for voters when an offer they voted for ships. Commission it
  • Shared commissions with the scope and cost split between organisations. Commission it
  • A public comment thread per offer, for detail on how it should work. Commission it

Where we point you to a specialist

  • A vote is a signal, not a contract. What we build, and when, is decided with the organisations that commission it and on a written scope.

Showing an offer’s status on the ledger itself is the next change to this loop.

Where this leaves you

If a ledger on this site names something you need, press I need this. If your organisation needs it built, press Commission it and we will reply with a scope. Either way, the ranking on the roadmap is what you pressed.

See what is most requested

The roadmap, the most requested offers from every ledger on the site, and how to commission one.

Open the roadmap

Frequently asked questions

Do I need an account to vote for an offer?

No. I need this is anonymous and needs no account, email or form.

Can someone vote many times for the same offer?

One vote per offer is counted per browser, and a second vote from the same IP address within 24 hours is not counted.

What happens when I commission an offer?

Your request reaches the founder with your name, work email, organisation and what you need, and we reply with a scope. When the offer ships, you are emailed once.

Does commissioning something add me to the newsletter?

No. The monthly email is a separate, unticked box on the form.

Where can I see which offers are most requested?

On the roadmap page, under Most requested right now, where one commission request weighs the same as five votes.

Share this article

LinkedIn X WhatsApp

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center