Hello, world - Easy Demos is in alpha
Anton Borodulin ·
Hello, my name is Anton
~15 years, four companies, the same job in different clothes - Tech Lead, Solution Architect, and now Engineering Manager at Wenco International Mining Systems in Vancouver, always enterprise software development. Different domains, different clients, but every one of those jobs agreed on exactly one thing.
Every sprint ends with the same choice: make the team's work look good, or sit down with the team and figure out what to do better next time. I tried different ways to make room for both, but it always came down to picking one over the other - never both, no matter how I rearranged the day.
The day I kept re-living
Sprint's wrapping up. Someone above me needs a summary - a stakeholder, a client, someone who doesn't live in Jira. So I pull the board, count what closed, eyeball the burndown, guess at what mattered, and write it all up into a Confluence page. Two or three hours, usually squeezed between the retro, daily calls, and whatever's on fire that day. Then I do it again next sprint. Then I hand it to a team lead, watch them reinvent it slightly worse, and fix it in a 1:1.
I did this at every one of those four companies. At some point I stopped assuming it was just my own bad time management and started wondering how many other teams were quietly paying the same tax - which is really the question this post is trying to answer with you, not just for you.
Right after New Year I decided to build a tool - mostly to help myself. Then somewhere in May it hit me that this could be a product, that it might help not only me but some of you too.
What it actually does
Connect Jira Cloud and pick a sprint, optionally add Azure DevOps for the CI/CD pipeline and repo signals underneath it, and about four minutes later you have a report that's pleasant to look at and safe to hand outside the team. Call it 30x over the manual version, give or take depending on how much archaeology you were doing before.
- Real metrics, zero spreadsheets. Velocity, completion, scope creep, burndown, cycle time - computed from the sprint, not typed by hand.
- CI/CD signals too. PRs, code reviews, pipeline health - the engineering story underneath the ticket story.
- Your voice, not just numbers. A simple editor for context and highlights. The metrics say what happened; you say why it matters.
- One link to share. A clean, read-only page, PIN-protected if it's sensitive, with controls to redact what shouldn't leave the room.
- Kind to your data. I spent something like a third of the build on this alone - I know the first question before anyone even considers the product is "is it safe? prove it." So tokens sit in an encrypted vault, reports are private by default, public pages minimize what's exposed, and you don't have to take my word for it - check the Trust Center.
That last one took real work: a full Aikido pentest and remediation pass during alpha, and Aikido's continuous monitoring now scores joinreadout.com at 99% against SOC 2 and 100% against ISO 27001:2022 (not certified yet - that's still on the roadmap, but the posture is real).
Seven languages, four themes, and it renders fine on whatever device your stakeholder actually opens the link on.
I'm not fully sure yet which of these matters most to you - probably not the ones I'd guess. That's a big part of why I'm posting this instead of quietly shipping it.
Why "alpha" and not "beta"
Because it's early, and I'd rather undersell the stage than oversell it. Sprint reports are the part that's actually built and live - I use it on my own sprints, and a few colleagues jumped in and started running theirs through it early on. Thanks to them, a lot of this got better, faster, and safer than it would have been if I'd kept it to myself - big kudos to those first few who put up with the rough early builds.
Milestone reports and release notes are next, and I'm building them right now. What I have in mind for release notes in particular, I haven't seen anywhere else on the market - that either means I'm onto something, or I've just spent too many nights on this to see it straight. We'll find out together.
Also on the list: deeper team-level insight - the patterns you only notice once you've run enough sprints to recognize one - and then AI on top of it. I already have ideas for where AI fits, drafting the narrative for you, but I'm not rushing it. Not another ChatGPT wrapper promising to do everything for you; I'd rather ship it safe, reliable, and actually worth using than ship it fast. For the full picture of what's coming and when, check the Roadmap.
Try it
Easy Demos is fully free during alpha. Connect Jira via SSO or a PAT - I did everything in my knowledge to make sure that connection is safe. Generate a report, check it, work through it with your team, share it with a colleague - I want this to actually be useful, not just a demo. See something broken? There's a "Report bug" button built right in - use it, I read every one.
One thing I'd hold off on for now: don't share a report link with a client yet, we're still in alpha. Take a screenshot instead and drop it into your Confluence page like before - just redact anything sensitive first (a screenshot can leak the same data a report does) and keep it to a workspace only your team can see.
If you see gaps or just want to tell me what you think, write to me - LinkedIn (or follow Easy Demos there), email, a personal Telegram DM, whatever's easiest. I'm thrilled to hear it.
One more thing before I go. Nobody told me I could stop having a day job to build this, so I didn't - four months of this got built at night and after hours, on top of a full work day, every day. My family lived through that with me. Thank you, genuinely, for tolerating it.
Now let's find out whether anyone besides me actually wanted this.
Anton