Operations-heavy product work
Bella AI was built around real operational flows: students, attendance, assessments, tenant boundaries, role access and realtime kiosk check-in/out.
Internal tools and automation
Internal tools, admin panels and integrations for teams with messy operations.
I build the operational software behind small teams: dashboards, admin flows, role-based access, imports, reports, automations and third-party integrations.
When this helps
This page is for product and operations people who feel the team is losing time in spreadsheets, manual status checks, fragile scripts or admin screens that do not match the real workflow.
Built for
Product/ops teams replacing spreadsheets with real workflows.
Small companies that need dashboards, admin panels or role-based tools.
Teams with repeated manual work across email, forms, CRMs, APIs or databases.
Businesses that need practical automation with human approval where mistakes are costly.
Why this is credible
Permissions matter
I have worked with RBAC, Supabase Row-Level Security, invitation-based registration and role-aware UI/API paths.
Useful density
For internal tools I prefer dense, predictable screens for scanning and repeated work instead of decorative marketing UI.
Outcomes
- Operational screens that match how the team actually works.
- Role-aware access and safer flows for risky actions.
- Automations and integrations that reduce manual status work.
- A maintainable path for future reporting, imports, exports and admin changes.
Process
- Map roles, entities, states, repeated actions and failure costs.
- Pick one workflow where software will remove real friction.
- Build the UI, API, data validation and permissions together.
- Test the repeated path and document operational assumptions.
Relevant proof
The Bella AI case is especially relevant here: multi-tenant admin, attendance, assessments, photo capture, role-based access, realtime kiosk flows, monitoring and E2E tests.
FAQ
Can you automate a messy process without rebuilding the whole company?
Yes. The safest start is one workflow, one source of truth and a clear manual fallback.
Can you connect existing tools?
Yes. APIs, webhooks, auth providers, databases, CRMs and custom dashboards are all normal parts of this work.
Can you make it usable without a designer?
Yes. Operational UI should be clear, dense and predictable. It does not need to look like a landing page.
Start with one email
Send your email and I will ask for the missing context instead of making you write a long brief.
Contact me