Skip to main content

About

Built by someone who got tired of retros that went nowhere.

SprintPulse is built by Eloquent Bytes, a small software company in Finland, for teams that want honest retrospectives to turn into visible improvement.

Vito Botta, founder of SprintPulse

Vito Botta, founder

A practical tool from someone who has watched the same unresolved topic return sprint after sprint.

I built SprintPulse because the hardest part of retrospectives was rarely the meeting itself. Teams could name the problem. They could agree it mattered. Then the action item would disappear into a document, a chat thread, or someone's memory.

After years of running and joining retrospectives, I wanted a tool that respected the conversation but did not leave the facilitator carrying the follow-up alone. SprintPulse is intentionally focused on the loop after the discussion: summarize the themes, assign owners, sync the work, and check whether things improved.

Eloquent Bytes is a small company, and that is part of the product philosophy. Support is direct, decisions are practical, and the product does not need a committee to fix something that is getting in your team's way.

Experience

30+ years

Building software across product, platform, infrastructure, and teams.

Support

Direct

When you reach out, you are close to the person who can actually improve the product.

Data care

EU hosted

GDPR-minded hosting for conversations teams often treat as sensitive.

SprintPulse AI summary showing themes and action item suggestions

Why this shape

SprintPulse is opinionated about what a retro should produce.

It should give every person a voice, not only the loudest people in the room.

It should leave behind a clear summary, not a set of scattered sticky notes.

It should create owned work, not vague intentions that depend on someone's memory.

How I think about trust

Small should not mean casual.

Careful scope

SprintPulse does not try to become every agile tool. It focuses on retrospectives and the follow-up they create.

Clear pricing

Small teams can start free, and paid plans are priced per team rather than turning every guest into a negotiation.

Sensitive conversations

Retro feedback can contain real workplace friction, so privacy and access control are treated as product basics.

Direct feedback loop

Bug reports and product requests do not travel through layers of process before they reach the builder.

Try the product

See whether SprintPulse makes your next retro easier to finish.

Create a board, invite your team, and leave with a summary plus tracked action items. Free for up to 10 users.

Next sprint follow-up

Generated from the retro summary

Synced

Set daily PR review windows for the platform team

Owner: Maya Due: Friday Jira SPRINT-42

Check next retro: did review wait time drop?

SprintPulse keeps the action tied to the original theme.