A note from the founders
Why we built ReqTwin
We started ReqTwin because we kept watching the same thing happen on project after project: a requirement gets written down once, early, and then it's on its own.It moves through a dozen documents, three different tools, and however many people touch the project between kickoff and handover. Slowly, quietly, it drifts from what actually got built.Stuart saw this from inside project delivery: project managers who couldn't tell you, without a week of digging, whether a spec was actually met. Design leads coordinating changes that never made it back to the source document. O&M managers handed the keys at the end, inheriting a gap nobody owned.Carlos saw the other half of it: schedules and requirements living in completely different worlds. The programme does its own thing in one tool, while requirements sit in a spreadsheet, or a SharePoint site, or both, going stale the moment nobody's looking.ReqTwin is what we built to close that gap. One place where requirements, ITP sign-off, BOM, and programme milestones stay linked to each other, so proving a requirement was actually met doesn't take a week of digging through old documents.We're both based in Melbourne, and neither of us set out to build "requirements software." We set out to fix the part of every project that everyone inherits and no one owns. If something in ReqTwin doesn't help a team prove a requirement was actually met, it doesn't earn its place in the product, that's still the only rule we hold ourselves to.Thanks for taking the time to read this. Reach out any time, we mean that.
- Stuart & Carlos
Stuart CarrollCo-founder
Carlos GrebloCo-founder