Case study

Contract Hub: a contracts database, rebuilt for the web

A Microsoft Access database that tracked contracts, task costs and employees, rebuilt by AccessToWeb.app as a browser-based application. Every screen below is the delivered software, running on demo data.

Contract Hub dashboard listing six open contracts with owner, status, expiry date and budget remaining, headline cards for committed budget and task cost to date, and a rail of contracts expiring within 30 days — The dashboard: every open contract, its budget position, and what expires next.

One screen answers the morning question

The dashboard opens on the question the old database made you dig for: what is open, what has it cost so far, and what needs attention. Six open contracts, $1,049,000 committed, $562,400 spent through tasks, and two renewals inside 30 days, all computed live from the same records the team edits. The expiring-soon rail does the chasing that used to depend on somebody remembering.

Every figure on this screen is a link, not a report you run: click through any contract row and you land on the live record behind the number.

A single contract page showing owner, effective and expiry dates, a budget burn-down bar reading 121,400 dollars spent of 180,000, and a task table with priority, status, cost, days and percent complete — A contract page: the burn-down bar shows budget consumed by tasks against days used.

Every contract carries its own budget story

Each contract page pairs a budget burn-down (67% of budget consumed against 146 of 220 days used, in the example above) with the task list that produced it: priority, status, cost, days and percent complete per task, totalled at the foot of the table exactly the way the old Access form totalled it. Adding a task moves every number upstream, including the dashboard, immediately and for everyone.

The reports screen offering eight print-ready PDF outputs including contract balance sheet, open contracts, contract tasks, tasks by assigned to, employee address book and employee phone list — Eight print outputs, generated as PDFs from live data.

The Access reports survived the move

Reports are where migrations usually stall, so they were rebuilt one for one: the contract balance sheet (budget against task cost per contract), open and completed contract listings, task reports grouped by priority and by employee, and yes, the employee address book and phone list. If those last two sound like classic Microsoft Access report names, that is because they are: the point of a rebuild is that the outputs people rely on keep existing, now as one-click PDFs from live data instead of a report someone runs from a desktop that has Access installed.

What changed underneath

One shared application in the browser instead of a file that opens on machines with Access on them.
Budgets, task costs and expiry chasing computed live instead of on demand.
Search across contracts and owners from any screen.
The client owns the source code. No per-user licence, no subscription, no platform it cannot leave.

Curious what your own database would look like on this side of a rebuild? The free Migration Blueprint maps every form, query and module and comes back with a fixed quote within 24 hours.

About the data in these screenshots: client work here is covered by an NDA by default, so every company name, person and dollar figure shown is fictional demo data. The software is the real delivered application.