Prepared by WasilaDev · for Makan360
Platform Discovery
Let's shape the Makan360 platform.
A quick, tap-through brief — mostly choices, little typing. Answer what you can; anything you skip, we'll shape together. Grouped into 8 subjects from our meeting.
STEP 01
Platform scope & the existing CRM
Understanding what the full platform covers, and how it relates to the CRM already delivered.
1.1The current CRM (Phase 1) is delivered and accepted. What's the intent for it? (biggest driver of scope)
1.2Major modules in the full platform beyond the CRM (pick any)
1.3Distinct user types (pick any)
STEP 02
Data & infrastructure
The database and cloud decisions raised in the meeting.
2.1Firebase vs Postgres — the preference
2.2Main driver behind that preference (pick any)
2.3Which cloud will Makan360 standardize on? (Microsoft stack ruled out)
2.4If we migrate off the current stack, existing data should be…
STEP 03
Repository & ownership
Setting up the new Makan360-owned repository and access model.
3.1On the new Makan360 GitHub, access model for the WasilaDev team
3.2Licensing / open-source policy to follow from day one (pick any)
STEP 04
CI/CD, environments & testing
Pipeline, environments, and the testing to build into the Definition of Done — this sizes each sprint.
4.1Dev, Staging/QA and Prod are confirmed. Who owns & pays for the cloud resources?
4.2Automated testing in the Definition of Done (pick any)
4.3CI/CD tooling preference
STEP 05
Workflow engine, AI & automation
Turning the automation and AI vision into concrete, scopeable requirements.
5.12–3 concrete example workflows or automations you want the engine to handle
5.2Which AI capabilities are priorities? (pick any)
5.3Any preferred AI providers or constraints?
STEP 06
Mobile app
Scoping the mobile side that shares the same backend.
6.1Mobile app approach
6.2Offline capability
STEP 07
Documents & process
The source documents and process items that gate an accurate estimate.
7.1Can you share both platform-vision documents to reconcile with Abu Ghazi?
7.2The SRS (gating item for an accurate estimate) is authored by…
7.3When do you expect the MVP architecture plan on your side?
STEP 08
Commercial framing
How you'd like the eventual estimate structured — no numbers implied at this stage.
8.1For the eventual estimate, the model you have in mind
8.2Main point of contact for this platform
8.3Anything else we should know? (optional)
REVIEW
Review & send
Check your answers, then choose how to send them back.
📎 Vision documents, the SRS, and any brand or reference files aren't uploaded here — please attach them to your reply email.