Edgintel SaaS Developer

I am building Edgintel, a decision-intelligence SaaS that converts academic and career goals into structured execution pathways with timelines, tasks, documents, and measurable outcomes. This is NOT a chatbot, NOT a coaching marketplace, and NOT an LMS. All product logic, pathways, and sequencing are already defined by the founder.
Your role is to implement a fixed system, not redesign or reinterpret it.

What needs to be built (MVP – Phase 1):

1. A structured onboarding flow that captures user goals and constraints (education, country, timeline, discipline, funding needs, availability).

2. A rules-based roadmap generator that outputs a personalised 12–24 week execution plan.

A user dashboard that shows:

1. weekly tasks
2. deadlines
3. progress status (on track / at risk)
4. A document workspace (“Vault”) where users can create, upload, version, and revise documents such as CVs, SOPs, proposals, cover letters, etc.
5. A task and accountability system with due dates and progress tracking.
6. Stripe subscription payments (monthly and annual).
7. Secure user authentication.

A simple admin panel to manage:

1. pathways
2. mentoring modules
3. tasks
4. templates

What this project is NOT:

1. Not an AI experiment
2. Not a content platform
3. Not open to feature ideation
4. Not open-ended

Technology preference:

1. Bubble, FlutterFlow, or similar no-code / low-code platform preferred for MVP
2. Open to full-stack only if speed and clarity are demonstrated
3. Clean database design and scalable logic required

Required experience:

1. Proven experience building SaaS products with structured logic or workflows
2. Comfortable working strictly from a founder-defined brief
3. Experience with dashboards, onboarding flows, and subscriptions
4. Ability to work milestone-by-milestone

Screening questions (must be answered):

1. Share a live SaaS product you built that involved decision logic or workflows.
2. How do you work when the product logic is already defined by the founder?
3. What would you not change even if you personally disagreed?
4. How do you prevent feature creep in MVP builds?

IMPORTANT NOTE:
Please NOTE that I am building decision infrastructure, not a generic app.