Phase-1 Property Portfolio Manager
Budget: $3,000 – $5,000 AUD
I’m kicking off Phase 1 of a web platform that lets property investors and their accountants ditch spreadsheets and bring everything into one place. The system must handle both residential and commercial assets held under individual, trust, company or SMSF structures, then turn the raw data into clean, tax-ready reports.
What I need built in this first release:
• A secure module for adding and editing properties, with fields that suit houses, apartments, warehouses and office spaces.
• Live bank-feed integration so clients can link their transaction accounts and loan facilities (Plaid, Yodlee or a comparable aggregator are fine—make a case for your preferred API).
• A rules-based transaction categoriser that learns over time yet allows manual overrides; all debits and credits must map cleanly to income, expense or loan principal/interest buckets.
• Core dashboards that roll everything into a running profit-and-loss and a downloadable statement accountants can slot straight into their software.
Please architect the back end for growth—future phases will add mortgage-broker and planner tools—yet keep the scope here to the four bullet points above. I’m happy to discuss stack recommendations (Node/TypeScript, Python/Django, or another well-supported framework) as long as you outline:
– your proposed data model for multi-ownership structures
– how you’ll secure bank connections and stored credentials
– sprint breakdowns with milestones and release criteria
Deliverables are the repo, deployment scripts and a brief technical document that shows another developer how to stand up the app in a clean environment.
What I need built in this first release:
• A secure module for adding and editing properties, with fields that suit houses, apartments, warehouses and office spaces.
• Live bank-feed integration so clients can link their transaction accounts and loan facilities (Plaid, Yodlee or a comparable aggregator are fine—make a case for your preferred API).
• A rules-based transaction categoriser that learns over time yet allows manual overrides; all debits and credits must map cleanly to income, expense or loan principal/interest buckets.
• Core dashboards that roll everything into a running profit-and-loss and a downloadable statement accountants can slot straight into their software.
Please architect the back end for growth—future phases will add mortgage-broker and planner tools—yet keep the scope here to the four bullet points above. I’m happy to discuss stack recommendations (Node/TypeScript, Python/Django, or another well-supported framework) as long as you outline:
– your proposed data model for multi-ownership structures
– how you’ll secure bank connections and stored credentials
– sprint breakdowns with milestones and release criteria
Deliverables are the repo, deployment scripts and a brief technical document that shows another developer how to stand up the app in a clean environment.