Budget: 1200 USD Deadline: 10 days
Regarding the price - 350 USD is enough for a short entry into the project, repository review, service launch, risk map, and 1 small MR. Completing subscription - billing with RevenueCat, abuse protection, notifications, analytics events, comments, gamification, deduplication, plus tests and refactoring for this amount is unrealistic. A realistic first engineering phase is 1200 USD and 10 working days, after which we can break it down by services.
Look, there’s a nuance - I opened Drive and the document with updates. It’s clear that MessageKit, Temporal, events between Flow Engine, Learning, and Automations, RevenueCat webhook, idempotent token log are important, not just CRUD. The Figma with current access needs to be additionally verified after granting view access. Overall, it’s fine, but without preliminary decomposition, it will be a lottery, and a lottery in billing is usually more expensive than development =/
Entry plan
> set up the project locally and check 11 services
> identify stable API contracts for the frontend
> close one priority block via GitLab MR
>> most often I would start with billing - RevenueCat - tokens - abuse, because that’s where the money is, webhook repeats, and security
> add unit and integration tests for critical scenarios
> provide a list of remaining services with stage estimates
Questions
> Is there access to GitLab, .env.example, docker compose, and test keys for RevenueCat?
> What is a higher priority for the first MR - billing or notifications?
Similar projects Ingello
> https://business.ingello.com/fractal - complex event architecture and agent processes
> https://business.ingello.com/platforma - corporate platform with roles, business logic, and integrations
> https://business.ingello.com/forma-bpm - processes, events, and managed logic
Main page of Ingello for FLH - https://systems-fl.ingello.com