AdminRent — residential management ecosystem
Role: Sole architect & engineer · Web + API + Mobile + Compliance microservice · Spec-driven, AI-augmented workflow
LATAM residential building managers juggle multi-owner accounting, recurring expenses, amenity bookings, and government-mandated e-invoicing across WhatsApp, spreadsheets, and outdated software. No unified, role-aware, mobile-first system that complies with Paraguay's SIFEN/DNIT digital invoicing.
A full ecosystem: web admin (Next.js 16), API (Flask 3), mobile app (Flutter 3), and a multi-tenant e-invoicing microservice (SIFEN-Core) with XAdES-BES digital signatures. Designed offline-first, role-aware (Owner / Tenant / Admin), and tax-compliant by default.
220+ commits in 2 months, 44+ production deployments across Vercel + Railway. Spec-driven dev: every feature has a written design + plan + tests before code. SIFEN-Core productized as standalone SaaS — AdminRent is its first tenant, designed to be sold to other LATAM SaaS too.
adminrent-frontendManager & owner dashboard. Multi-residential switching, financial reports, expense scheduling, transactions ledger, owner-tenant role flows. Vercel · 28 deploys · 129 commits
adminrent-backendREST API. Multi-tenant data isolation, owner-dashboard service, recurring expenses + scheduler, JWT auth (Supabase), Excel/PDF exports, transactional email. Railway · 16 deploys · 93 commits
adminrent-mobileOwner / Tenant native app. Offline-first with sqflite cache, FCM push notifications, role-adaptive hub, multi-residential switching, amenity booking with hourly availability, payment claim photo capture.
SIFEN-CoreMulti-tenant SaaS microservice for Paraguay's mandatory e-invoicing (SIFEN/DNIT). XAdES-BES digital signatures, encrypted certificate storage, CDC algorithm, SOAP integration with government web services. Productized to be resold.
- • Each feature starts with a written design spec (problem · constraints · API contracts) and an implementation plan (chunked tasks, TDD checklist)
- • Plans live in
docs/superpowers/specs & plans— versioned, dated, reviewable - • Tests are written before code — pytest for backend, Jest for SIFEN-Core, flutter_test for mobile
- • Audits in
docs/superpowers/auditsfor post-ship reviews
- • Claude Code (Anthropic) — primary coding agent, sub-agent orchestration via superpowers framework
- • Supabase MCP (Model Context Protocol) — Claude has live, read-aware access to schema for migrations + queries
- • Cursor for inline edits, Gemini CLI for cross-checks
- • Brainstorm sessions logged in
.superpowers/brainstorm— reusable context for the agents - • Shipping nearly daily as a one-person team because the AI workflow handles boilerplate, test scaffolding, migration drafts, and refactors