My part
Mapped provider states into one order model and built the founder dashboard, internal queue, and integrations with Kotlin/Spring Boot and PostgreSQL.
Full-stack product / co-founder
Rely
A Spanish-first company-operations product combining a customer dashboard, an internal operations queue, and 6+ connected services.
At a glance
- Period
- October 2023 to present; side project during Aivo employment (October 2023 to July 2024), concurrent with Acelera since January 2026
- Role
- Co-founder; product and full-stack engineering
- Team
- Two developers with mutual code review
- Users
- LATAM founders and the operations team supporting them
- Status
- Live company-operations product
- RoleProduct + full-stack engineering
- Integrations6+ connected services
- FrontendReact + TypeScript
- BackendKotlin + Spring Boot
Tradeoff
Combine provider updates into clear customer actions while preserving the operational checks needed before filings, payments, and other sensitive changes.
Evidence
The public rely.business site, plus real dashboard and pricing screens with personal data removed.
Synthetic walkthrough
Dashboard, next action and operations queue
Follow one order in three steps: what the founder sees, the action they need to take, and how operations picks it up.
Illustrative reconstruction with synthetic data. This is not an original Rely screen or an exact replica.
- Company: filed
- Identity check: pending
- Documents: 1 pending
Next step: upload proof of address
01
The operating constraint
A formation order moves through filings, banking, documents, payments, deadlines, and support. Each provider reports state differently. Founders need a useful answer to one question: what happens next?
02
One company, two working views
I designed the shared state model, founder dashboard, and internal queue. Customers see progress and required actions. Operators see ownership, provider state, documents, exceptions, and the context needed to act.
03
Make the next action visible
The shared order connects customer context, missing documents, provider state, and required actions. Sensitive changes stay behind explicit approval.
04
What is running
The frontend and admin tools connect to Kotlin and Spring Boot services, PostgreSQL, Auth0, Stripe, document storage, formation providers, and 6+ connected services.
05
Observed result
Around 40 companies have passed through the founder dashboard. In production, a founder can create a company and receive the EIN and formation documents through an automated flow, while registry approvals and payments keep their own checks. Operators work from a shared queue with provider state, documents, and visible approval boundaries.
Project linksrely.business