AAVIRO.ONE

TechnicalDept · AVIRO.ONE

“How much of this sprint was actually maintenance?”

See how much of your team’s time is feature work — and where debt keeps biting.

Developers feel the drag every day. Leadership asks for a number. You open a spreadsheet of guesses — while the same fragile files get patched again.

TechnicalDept turns your Git history into a clear feature-vs-maintenance ratio and a shared backlog of the files that hurt most.

₹500 / developer / month · or ₹15,000 Team ≤20 seats

technicaldept · overview

Last 30 days

Feature vs maintenance

Team
Feature 62%Maintenance 38%

Classified

847

Flagged

24

Repos

3

Top risky files

Backlog

  • src/billing/settle.tsHigh
  • api/auth/session.tsHigh
  • lib/legacy/import.tsMed

The problem

Debt stays invisible until it costs a feature

Small and mid-size teams know maintenance is eating capacity. They just can’t prove it — or point to where to fix it first.

01

Anecdote vs deadline

Engineering asks for time to clean up. Product hears a story, not a number. Feature work wins by default.

02

Pain buried in Slack

Risky files live in verbal complaints and tribal knowledge. Nothing ranks what causes repeated bug-fix churn.

03

Heavy tools, wrong job

Static-analysis platforms are priced and scoped for large orgs. Most teams need visibility and prioritization — not another code scanner.

The shift

Connect the repo. Get the ratio. Rank the pain.

TechnicalDept is a lightweight multi-tenant dashboard for product teams and agencies. Read-only Git access. Configurable classification. A backlog the whole team can use.

1

Connect GitHub or GitLab and select the repos that matter.

2

Every commit/PR is classified as Feature Work or Maintenance/Fix Work.

3

Flag risky files, vote with the team, and rank by severity + bug-fix touch frequency.

From connect to planning conversation

From OAuth connect to a ratio you can take into planning.

  1. 01

    Connect

    Admin signs in with GitHub or GitLab OAuth, picks tracked repositories, and invites the team. Read commit metadata and file paths — never file contents, never push access.

  2. 02

    Classify

    Incoming commits are labeled Feature or Maintenance using configurable keywords and change heuristics. Admins can override with an audit trail when the model gets it wrong.

  3. 03

    See the ratio

    Overview shows feature-vs-maintenance % over a date range, with trends and team or individual filters — framed for planning, not surveillance.

  4. 04

    Prioritize debt

    Contributors flag painful files with severity. The backlog ranks what keeps breaking. Open file detail for touches, timeline, and history.

Chapter 01

One number leadership can trust

Feature-versus-maintenance share, trend over recent weeks, and filters for the whole team or a single contributor. Export when you need the ratio in a deck or planning doc.

  • Team & individual views
  • Trend over selectable ranges
  • CSV / PDF export

Overview

Maintenance share · 38%

Feature work trending up

Chapter 02

A backlog that ranks real pain

Anyone with Contributor access can flag a path and set severity. Duplicate flags become votes. Maintenance touch frequency and last-touched dates keep the ranking honest.

  • High / Medium / Low severity
  • Votes + touch frequency
  • Search, filter & sort

Debt backlog

Ranked by pain

billing/settle.tsHigh · 18 touches
auth/session.tsHigh · 14 touches
legacy/import.tsMed · 9 touches

Chapter 03

Classification you can tune

Per-workspace rules catch your commit style. Try a message before you save. Manual reclassify recalculates the ratio with who changed it and when.

  • Keyword & heuristic rules
  • Live commit tester
  • Admin override + audit

Rules

Try a commit message

fix: null check in settle path
→ Maintenance / Fix Work

Pricing

Affordable enough to keep the ratio on.

Priced for small and mid-size teams — well below heavy static-analysis platforms — so the ratio and backlog are actually affordable to keep on.

Per seat

₹500per developer / month

Pay for the seats you need. Built for growing product teams and agencies.

  • GitHub & GitLab connect
  • Feature vs maintenance overview
  • Debt backlog, flags & votes
  • Team dashboard & reports
  • Classification rules editor
  • Workspace roles (Admin / Contributor / Viewer)

Team

₹15,000per month · up to 20 seats

Flat team tier when you need everyone under one predictable invoice.

  • Everything in Per seat
  • Up to 20 developer seats
  • Admin reports & exports
  • INR billing via Razorpay (planned)

Pricing is a working assumption for AVIRO.ONE launch materials and may be finalized before public billing. Contact us for early access.

Voices

What changes when debt becomes a number

“We finally walked into planning with a maintenance share we could defend — not a gut feel from Slack.”

Engineering manager

Product team · pilot profile

“The backlog made the ‘scary files’ conversation concrete. High severity plus repeated bug-fix touches rose on their own.”

Tech lead

Agency squad · pilot profile

“It’s planning data, not a personal scoreboard. That framing mattered for getting contributors to flag files.”

CTO

Mid-size product org · pilot profile

Still wondering

A few straight answers

Git access, classification, pricing, and what we deliberately leave out.

Engineering managers, CTOs, and product engineering teams (including agencies) who need a defensible feature-vs-maintenance number and a shared way to prioritize risky files — without buying a heavy static-analysis platform.

The next step

Stop estimating maintenance.
Start measuring it.

Connect GitHub or GitLab, get a feature-vs-maintenance ratio, and put the riskiest files on a ranked backlog your team actually uses.