{"slug":"decision-register-service","name":"Decision register service","category":"Management","customer":"Department heads handling frequent cross-team decisions","problem":"Teams cannot locate the current decision or its rationale.","value":"For department heads handling frequent cross-team decisions, turn approved meeting notes and decision records into versioned decision register. Address the recurring problem: teams cannot locate the current decision or its rationale. The value hypothesis is a more complete, reviewable deliverable with less repeated preparation; the pilot must establish whether that benefit is real.","format":"Operational coordination portal","screens":"Key screens: Decision search, rationale card, review calendar. Use a queue or timeline as the opening view, with clear owners, dates and current states. Each case opens into its source context, proposed actions and discussion. Give external participants a limited form or status page. Make the next required action visible without opening every record. In this product, the first view is decision search, followed by rationale card and review calendar.","functionality":"1. Capture decisions. 2. Name owners. 3. Attach evidence. 4. Record alternatives. 5. Identify superseded decisions. 6. Schedule reviews.","workflow":"Create a case from approved inputs, identify required actions, confirm owners and dates, request missing information, approve proposed communications or changes, track completion, and retain a handover record. Start with approved meeting notes and decision records and finish with versioned decision register.","ai":"Extract candidate actions and relevant context, classify requests and draft communications. Use explicit rules for scheduling, state transitions and permissions. People confirm obligations and approve consequential actions before execution.","inputs":"Approved meeting notes and decision records","deliverables":"Versioned decision register","admin":"Role permissions, task ownership, deadlines, reminders, approval gates, exception handling, action history, duplicate prevention and reversible configuration.","mvp":"Begin with department heads handling frequent cross-team decisions and one recurring use case. Build the first two modules: capture decisions; name owners. Provide operator assistance for the third module: attach evidence. Deliver versioned decision register through a manual review queue. Perform other necessary full-scope functions manually during the pilot. Include all applicable access, accuracy and professional-review controls from the start.","expansion":"After paid pilots establish value, automate the remaining modules: record alternatives; identify superseded decisions; schedule reviews. Add one validated source integration, reusable customer configuration and recurring delivery. Expand to additional teams, document formats or languages only after testing the new scope.","usp":"Shows which decision is current and why earlier choices changed.","defensibility":"Customer-specific workflow rules, reliable handoffs, operational history and integrations that make the service part of daily work. For this solution, build around shows which decision is current and why earlier choices changed. This advantage requires execution and accumulated customer trust; the base model alone is not a defensible asset.","alternatives":"Shared inboxes, spreadsheets, task boards and existing workflow automation products. Differentiate on this specific proposed advantage: shows which decision is current and why earlier choices changed. Test it against the buyer's current method on the same task. Competitor coverage and uniqueness have not been established.","revenue":"Test USD 750-2,500 setup plus USD 200-800 monthly for one bounded workflow and team. Cap case volume and implementation scope. Larger operational integrations need separate quotes. Prices are hypotheses.","costs":"Workflow configuration, integration maintenance, model calls, notification delivery, exception support and monitoring.","integrations":"Team updates, calendars, project records and agreed management routines. Calendars, email, task managers and relevant business records. Use draft actions and supervised handoffs first, then enable only specifically authorized writes. These are candidate integration categories, not verified supported connectors.","dependencies":"Explicit state definitions, owner mapping, approval rules, idempotent actions, notifications and recovery procedures. Workflow reliability matters more than fluent text.","pilot":"Run one recurring workflow with a small team. Track every handoff and exception, verify completed actions, and compare handling time and missed commitments with the prior process. For this solution, use approved meeting notes and decision records and evaluate versioned decision register. Agree success thresholds with the buyer before starting; collect a baseline for retrieval success, contradictory instructions. A positive signal is payment and repeat use with acceptable quality and delivery cost, not a favorable demo reaction alone.","plan30":"Week 1: interview five prospective buyers in this segment: department heads handling frequent cross-team decisions. Ask to see a recent example of the problem and their current process. Week 2: prepare this demonstration using authorized or synthetic material: a searchable department decision register. Week 3: present it through operations consultancy partners and seek one narrowly scoped paid pilot. Week 4: review retrieval success, contradictory instructions, total delivery effort and a concrete renewal decision before increasing scope.","metrics":"Retrieval success, contradictory instructions","channels":"Operations consultancy partners","leadMagnet":"A searchable department decision register","message":"Decision register service for department heads handling frequent cross-team decisions. Shows which decision is current and why earlier choices changed. Demonstrate the claim through a searchable department decision register.","retention":"Report completed actions and recurring exceptions. Maintain the workflow as policies change, then add one adjacent handoff with clear ownership.","controls":"Confirm owners, decisions and commitments. Keep employee discussion notes access-controlled and avoid covert individual performance inference. Validate source access and reviewer availability during the pilot. Maintain customer-level access, data deletion controls and a record of final approvals.","crossSector":"Operations; Human Resources","fn":["Capture decisions","Name owners","Attach evidence","Record alternatives","Identify superseded decisions","Schedule reviews"],"sc":{"opp":8,"pain":6,"feas":6,"now":7},"phases":[{"name":"MVP","scope":"One buyer segment, one recurring use case; first modules: capture decisions; name owners. Manual review in the loop.","time":{"days":5,"label":"5 days"},"usd":9500},{"name":"Paid pilot","scope":"Accounts, roles, review states, audit trail and the first integration, hardened for two to three paying pilot customers.","time":{"days":6,"label":"6 days"},"usd":12000},{"name":"Full product","scope":"Remaining modules: record alternatives; identify superseded decisions; schedule reviews. Self-serve onboarding, billing, monitoring and the wider integration set.","time":{"days":12,"label":"2 weeks"},"usd":17000}],"running":[{"stage":"MVP and paid pilot","note":"about 3 customers","hosting":[30,60],"ai":[40,90],"total":[70,150]},{"stage":"Full product","note":"about 50 customers","hosting":[110,210],"ai":[280,560],"total":[390,770]}],"total":38500,"complexity":0.67,"days":23,"shot":true,"demo":true}