CEDX Services · Projects & Delivery
Services runs the delivery book end to end: 320 engagements, 48 SOWs with hours remaining, and the margin on every row — 53% portfolio margin against a 34% target, with the 17 at-risk engagements named and priced.
The alert worth reading is the polite one: “Billable util 124% vs 75% target — above target, protect quality.” A services tool that only cheers is not watching the same business you are.
Runs on demo data. Dollar figures are the seeded demo portfolio's, not billing data.
What it is
Forty-eight statements of work with type, status, value, hours and hours remaining on every row — 36 signed live, 39,105 hours left across the view. A fixed-price SOW at 2,400 hours with 850 left is a different conversation at week 31 than at week 39.
Every engagement carries budget, billed and margin — the average across the view is 42%. The type and status chips cut the book the way partners actually ask about it: Fixed-price closing work, retainers on hold, T&M in active delivery.
320 tasks across the engagements — 296 open, 7,544 estimated hours — each with its engagement key, status, estimated versus actual hours and a billable Yes/No flag. Non-billable knowledge transfer is visible as non-billable, not absorbed.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/services.
01 — Overview
193 active engagements, utilisation 124% against a 75% target, margin 53% against 34%, and $461K of time sitting unapproved. Portfolio health reads 20% and the alerts say why: one engagement at margin 15% with burn 92%, 160 entries pending approval, and utilisation high enough to be a quality risk.
02 — Engagements
The ledger: key, engagement, client, type, status, budget, billed, margin, PM. Cut it by T&M, Fixed or Retainer; by Active, Pipeline, Closing or On Hold — the counts and the dollars follow the filter.
03 — SOWs
Forty-eight SOWs sorted by value with hours and hours left on each: the largest at $680K has 850 of 2,400 hours remaining; a draft sits unsigned at full hours. The book's 39,105 remaining hours are the delivery organisation's real backlog.
04 — Tasks
Every engagement decomposes into tasks with estimates, actuals and a billable flag. The blocked chip isolates the 89 that need attention; the billable chip shows the 211 that earn. The margin board upstream is built from these rows, not from a monthly estimate.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Owns the row: budget, billed, margin and the tasks underneath. A 95% margin-risk score with burn at 92% is their Monday, not their quarter-end.
margin risk · 17 engagements
Staffs the SOWs against the roster: 39,105 hours remaining is demand, and the delivery bench either covers it or it does not.
hours remaining · 39,105
Logs against the task, sees the billable flag on the row, and knows which of their hours the client pays for — because the ledger says so.
billable open · 211 tasksThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
The work is papered as an SOW: type, value, hours. Draft is a visible state — unsigned work does not silently enter the delivery book.
The SOW's hours become demand on the roster. 39,105 hours remaining across the book is the number the resourcing conversation starts from.
Tasks carry estimates, actuals and the billable flag; time is approved against the engagement. Unapproved time is a dollar figure — $461K — not a shrug.
Billed reconciles against booked, margin against target. The 17 engagements at risk are named while there is still time to change the answer.
One record
The services book only balances if scope, staffing, time and billing read the same record. That is the estate's job, not a monthly export's.
The $461K of unapproved time on this overview is the timesheet approval queue, read at portfolio level.
CEDX ResourcingSOW hours become placeholders on the resourcing grid — the senior engineer a rollout needs at 24h a week.
CEDX InvoicingBilled against booked is only true if the invoice reads the same approved hours the engagement does.
CEDX ContractsThe SOW is a commercial document before it is a delivery plan; the signed state lives with the contract record.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your book, your rate card
Services with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/services. It runs on demo data.
From the rows underneath: budget versus billed per engagement, built up from tasks carrying estimated and actual hours with a billable flag. The portfolio reads 53% against a 34% target; the view average is 42%; both are printed where you can check them.
Because the target is 75% and the alert says so plainly: “above target, protect quality.” Sustained over-utilisation is how services businesses burn their delivery teams, and the product treats it as a risk, not a win.
Logged hours no manager has approved yet — $461K across 160 entries in the demo. Unbilled work you cannot invoice is a cash problem, so it sits on the overview as a card, not in a report.
Yes — the margin board scores them: 17 at risk (score ≥55) with $342K of portfolio dollars at stake, and the top row spells out why: margin 15%, burn 92%, $65K at risk on one engagement.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then check what your own unapproved-time number would be.