Roadmap
Agenoia is being built and validated with a live pilot customer. Here's where it stands.
Estimated implementation + real-customer-testing effort (in weeks) plotted against real-world value for PMs. Bubble numbers correspond to the task table below. Arrows show build dependencies. Several tasks share a similar cost/value estimate and start out stacked close together — drag any bubble to spread them out; positions are just for readability and don't change the underlying estimate. These estimates are directional, not committed — the point is to show scope and sequencing, not a fixed schedule.
Task list (detail table)
| # | Task | Category | Est. weeks | Value (1-10) | Status | Depends on |
|---|
Agenoia can answer questions about live project data — for example unpaid invoices — with permission-aware answers that depend on who's asking. Query latency is currently around a minute; reducing that is the next focus.
Cleaning up formatting and rendering issues in responses.
Agenoia moves from read-only to proposing actions inside your project-management workflow — always as a proposal a human approves, never a silent write.
Agenoia participates in the email threads that already drive most project-management admin work today.
Self-model-driven staffing and negotiation with providers, within an explicit authority limit — see self-modeling.
How this is being validated
Rather than build in isolation, Agenoia is being developed against a real pilot: a translation agency automating the administrative side of project management, where projects are numerous, small, and closer to order processing than to full PM. That's a deliberately narrow, well-bounded starting point — details in before you deploy.