Selected work / Partner operations
A connected platform
for ResetData’s partners.
At Centuria-backed ResetData, Form From’s founder led engineering of a self-hosted partner platform covering deals, sales enablement and five user roles. Delivery combined application and backend development with practical AI-development sessions for the client’s engineers.
- The project
- A partner relationship management platform for ResetData’s channel business.
- Our contribution
- Platform engineering, delivery tooling and hands-on development of the team’s working methods.
- The continuation
- The team continued merging changes after handover, including hardening, testing and security work.
The task
Support different roles in the same sales process.
ResetData’s channel business involves administrators, channel managers, programme owners and business development managers. They share a process, but have different responsibilities within it.
The software needed to reflect those relationships across partner records, deals, sales resources, training and incentive programmes.
One platform. Different responsibilities.
- 01
Five roles with different responsibilities.
- 02
Channel managers, programme owners and BDMs.
- 03
Role-specific deal workflows.
- 04
Sales toolkit, training and incentive domains.
Our contribution
Connect the interface to the complete workflow.
Form From led application and backend engineering, connecting role-specific screens and actions with the underlying data model. A deal moving between people had to work across the interface, permissions, API and database.
The platform used React and FastAPI with a shared database, supported by Jira and GitHub delivery workflows. Practical sessions with two junior engineers used the team’s own product: specifying tasks, directing agents, reviewing implementations and releasing changes.
We also developed an in-app review tool that attached feedback to a screen and its state, then carried that context into an engineering ticket. It supported delivery of the partner platform.
The continuation
The team kept developing the product.
The delivered platform covered five user roles, partner and deal workflows, and a shared sales toolkit. The team continued merging changes after handover. Subsequent work included permission tests, security scanning, release controls and remediation of penetration-test findings.
That continuation matters alongside the software itself: the engagement helped the team develop a way to specify, review and improve its own product. The record supports that delivery outcome; changes in sales performance have not been measured here.
What this means for another project
Deliver the capability to continue.
Engineering and capability transfer can happen through the same work. Use real tickets to develop the product and the team’s judgement about task design, review and release.
Discuss a similar project