AAVIRO.ONE

TechnicalDept · AVIRO.ONE

“How much of this sprint was actually new features?”

See how much new-feature work your team ships — and which files get touched the most.

Developers feel the drag every day. Leadership asks for a number. You open a spreadsheet of guesses — while the same files keep eating bug-fix and improvement work.

TechnicalDept turns your Git history into a clear new-feature share and an automatic view of file activity — no manual logging, no personal scoreboard.

₹500 / seat / month · 7-day free trial · Razorpay

technicaldept.aviro.one

Last 30 days

New-feature share

Team
Feature 54%Bug 28%Improve 18%

Classified

847

Hot files

24

Repos

3

File activity

Auto

  • src/billing/settle.ts18 · bug-heavy
  • api/auth/session.ts14 · mixed
  • lib/legacy/import.ts9 · improve

The problem

Capacity trade-offs stay fuzzy without Git-backed numbers

Small and mid-size teams know bug fixes and polish steal runway. They just can’t show the split — or point to the hottest files first.

01

Anecdote vs deadline

Engineering asks for cleanup time. Product hears a story, not a ratio. Feature work wins by default.

02

Pain stays tribal

Risky areas live in Slack and head knowledge. Nothing shows which paths absorb repeated bug-fix and improvement touches.

03

Heavy tools, wrong job

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

The shift

Connect the repo. Get the ratio. See file activity.

TechnicalDept is a lightweight multi-tenant dashboard for product teams and agencies. Read-only Git access. Tunable 3-way classification. File activity built automatically from every sync.

1

Connect GitHub or GitLab and select the repos that matter.

2

Every commit is classified as Bug fix, New feature, or Improvement.

3

File activity ranks paths by touches — with who worked them and a 3-way split.

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 as Admin or Read-Only. We read commit metadata and file paths — never file contents, never push access.

  2. 02

    Sync & classify

    Sync each repo on demand. Commits are labeled Bug / Feature / Improvement from configurable keyword lists (match order: Bug → Feature → Improvement). Overview stays cache-first from your last sync.

  3. 03

    See the ratio

    Overview shows % new-feature work plus a 3-way breakdown, with trends and team or individual filters — framed for planning, not surveillance.

  4. 04

    Review file activity

    An automatic board surfaces hottest files: touch volume, bug/feature/improvement split, and top authors. Open any path for the full commit timeline.

Chapter 01

One ratio leadership can trust

New-feature share against bug fix and improvement work, trend over recent weeks, and filters for the whole team or a single developer — so planning conversations start from data.

  • Team & individual views
  • 3-way breakdown bar
  • Cache-first Overview

Overview

New feature · 54%

Feature 54%Bug 28%Improve 18%

Chapter 02

File activity that builds itself

No manual flagging. After sync, every touched path appears with touch count, severity from volume thresholds, who authored the changes, and how the work split across Bug / Feature / Improvement.

  • Auto from classified commits
  • Who touched + why (3-way)
  • Search, sort & file detail

File activity

Hottest paths

billing/settle.ts18 touches · bug-heavy
auth/session.ts14 touches · mixed
legacy/import.ts9 touches · improve

Chapter 03

Classification you can tune

Per-workspace keyword lists for Bug, Feature, and Improvement — plus a live “try a commit message” tester so the labels match how your team writes history.

  • Three keyword lists
  • Live commit tester
  • Per-workspace rules

Rules

Try a commit message

fix: null check in settle path
→ Bug fix

Pricing

One seat price. Seven days free.

One simple seat price — so small and mid-size teams can keep the ratio and file activity on without enterprise tooling costs.

7-day free trial — starts when you create a workspace

Per seat

₹500per seat / month

Every Admin and Read-Only member counts as a seat (minimum 1). Subscribe with Razorpay Checkout when the trial ends.

  • 7-day free trial on workspace create
  • GitHub & GitLab connect
  • 3-way classification (Bug / Feature / Improvement)
  • Overview ratio + File activity board
  • Team dashboard, reports & in-app notifications
  • Classification rules editor
  • Roles: Admin & Read-Only
  • INR billing via Razorpay

After trial or unpaid periods, Overview stays readable; Sync and Connect are soft-gated until an Admin subscribes.

Voices

What changes when Git history becomes planning data

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

Engineering manager

Product team · pilot profile

“File activity made the ‘scary files’ conversation concrete. Hot paths and bug-fix touches rose on their own after sync.”

Tech lead

Agency squad · pilot profile

“It’s planning data, not a personal scoreboard. That framing made it safe to filter by individual without turning into performance theater.”

CTO

Mid-size product org · pilot profile

Still wondering

A few straight answers

Git access, 3-way classification, File activity, pricing, and what we deliberately leave out.

Engineering managers, CTOs, and product engineering teams (including agencies) who need a defensible new-feature vs bug/improvement split and a shared view of hottest files — without buying a heavy static-analysis platform.

The next step

Stop estimating the split.
Start measuring it.

Connect GitHub or GitLab, get a new-feature ratio with Bug / Feature / Improvement breakdown, and review hottest files on an automatic activity board. 7-day free trial — then ₹500 per seat.