An AI project manager that works from your codebase, not your tickets

Meet Aiden: your AI software project manager

Every team without a project manager still has one: whoever gets asked “where are we on this.” Aiden takes on the status work. Turn your brief into approved requirements, check what is implemented, and see what remains with estimates grounded in your team’s history.

Talk to us See how Aiden works

Calendar authenticationIllustrative report

AidenStatus refresh complete

The API checks authentication. Sign-in and private calendar access still need work.

Account registration and API accessImplemented

The API hashes passwords and rejects requests without valid authentication.

Sign-in and session cleanupNot implemented

The UI still needs to send the token and clear private data when a session ends.

Private calendar dataDeviated

Event queries do not consistently restrict results to the signed-in owner. This differs from the approved requirement.

Project outlook

6 of 18 complexity points implemented. 12 points remain.

At 6 points per week, the remaining scope would take 10 working days. Weekends excluded.

Illustrative valuesForecast, not a commitment

An illustrative project report after a status refresh.

Paste your project brief
Approve the requirements
Check against the code
Estimate and forecast

Is this my problem?

The job that exists whether or not you hired for it.

Between deciding what to build and getting it in front of customers, somebody has to know where each project stands and whether what got built is what was agreed upon.

Get a shared view of scope, implementation, and estimates instead of piecing together status updates scattered across the team.

Three things that go wrong without it

01
Tasks are treated as the source of truth.
Using tasks as a source of truth relies on good intentions and manual coordination. Implementations change, tasks go stale, and ultimately only the code can tell.
02
What was agreed and what got built drift apart.
Nothing in the toolchain compares the two, so the gap shows up in QA, during product review, or from a customer.
03
Estimates have no connection to how your team works.
A guess at effort does not tell you how long the work will take. Your team’s completed work gives that estimate a starting point.

What it does on your team

Clear scope. Verified progress. Informed estimates.

You decide what to build and approve the requirements. Aiden checks the code and brings the evidence and estimates together in one project.

01 · Define

Start with what your team agreed to build.

Describe the project or paste a brief with acceptance criteria. Aiden prepares an overview and checkable requirements for you to review and approve.

Calendar authenticationScope review

People can sign in, use a private personal calendar, and sign out safely.

REQ-1 Registration and login return a token. Passwords are stored as hashes.

REQ-2 The UI signs users in and sends the token with calendar requests.

REQ-3 Calendar operations reject missing or invalid authentication.

2 more requirements: owner privacy and session cleanup

Illustrative requirementsYou review and approve

02 · Verify

See what is implemented, with evidence.

Refresh project status when you need an answer. Aiden checks relevant branches across your connected repositories and links each finding to the code, including where it differs from the agreed scope.

REQ-4 · Owner privacyCode assessment

AidenNot implementedDeviated

The requirement says users can see only their own events. This query returns events without filtering by owner.

Each finding includes an explanation and links to the inspected GitHub code, pinned to a commit.

Illustrative findingShown in your project

03 · Estimate

Put your team’s history behind the estimate.

See a complexity size and its reasoning for each requirement. Connect Linear for duration estimates from completed work, then forecast a finish from your delivery rate. Adjust the estimates when you know better.

REQ-2 · Sign-inEstimate

M · 3 complexity points

Touches the sign-in form, session state, and API requests. Allow for regression checks in a live service.

Predicted duration · 3.5 days

Six similar-size completed issues took 1, 2, 3, 4, 5, and 6 days. Their median is 3.5 days.

Adjust the size, duration, or historical comparison values when your context differs.

Illustrative historyConnect Linear to estimate time

Nobody’s job changes

Product still decides what. Engineering still decides how. Aiden holds the two together and tells you when they’ve come apart.

Product

What to build.

You bring the intent and acceptance criteria. Review and approve the overview and requirements before Aiden starts tracking the project.

Engineering

How to build it.

Engineering owns the approach and the code. Aiden checks relevant branches across repositories, including work that has not reached the default branch yet.

Aiden

Scope, status, and estimates.

A project summary grounded in code, with estimates informed by team history. You control the delivery rate and target date; Aiden shows the forecast and what differs from the plan.

Who built it

Two co-founders who kept getting asked “where are we on this.”

Christian Ciabattoni

Co-founder and CEO

“As a career software engineer with 10+ years of experience, I’ve seen so much time lost (including my own) simply trying to answer basic project status questions. That’s why I built Aiden to help do the time consuming work so that you can focus on the role you were hired for.”

Rowena Cheng

Co-founder and CRO

“Throughout my sales career, I’ve always had trouble getting a clear answer on where a feature I promised a customer is at and when it will be live. Being able to see it automatically in Aiden is an absolute game changer.”

Talk to us

Bring us one project.

Tell us about the team and what you are building.

Pricing

Custom pricing based on your team’s needs that scales proportionally to usage.

We reply within two working days.