The six checkpoints every CleenUI engagement hits — from the no-cost architecture review through the first year of product expansion.
A 30-minute call — no cost, no commitment. You bring your stack, your team shape, and your top three modernization questions. The architect tells you whether CleenUI fits, and if it does, the engagement shape: which modules you'll activate day one, and a rough timeline. If it doesn't fit, you still get 30 minutes of senior architectural guidance on your problem. No SDR, no sales hand-off.
After the engagement is scoped and licensed, you receive the full source code across all four tiers: React 18 frontend (61 accessible components), ASP.NET Core 8 Web API (524 documented endpoints), Azure SQL schema (300+ tables, 700+ stored procedures), and the 12-project background services solution (Azure Functions + WebJobs). Included: CLAUDE.md, OpenAPI 3 spec for all endpoints, Storybook component documentation, and Postman collection.
Architect-assisted provisioning of your Azure infrastructure: resource group, App Service, SQL Server, Storage Account, Function App, and Key Vault. Auth0 tenant setup and application registration. CI/CD pipeline configuration and staging environment first deploy. The goal by end of week one: your team has a working application running on your cloud infrastructure.
CLAUDE.md and the AI agent skills (Setup, Builder, Theme) are configured in your team's editors. The team understands the module architecture, the stored-procedure data access pattern, and the RBAC model. First domain-specific features — the things that make your product distinct — are in active development.
The team is self-sufficient. They're building, testing, and deploying without architect supervision on every ticket. Architectural office hours remain available for design questions on new domain areas — not for day-to-day delivery. The engagement shape at this point depends on what was scoped at Day 0.
New modules activated as the product scope grows. M09 AI Operations connected to your LLM vendor of choice. Optional background processing extended for your domain-specific async work. Ongoing access to the architect for strategic design questions on new directions.
The architect delivers the codebase, provisions the environment, onboards the team, and answers architectural design questions. The architect does not write your application code or manage your team’s day-to-day delivery.
The goal of the engagement is to get your team to independent production capability — fast. Most teams hit that within the first month. After that, the architect is available for strategic design questions, not as a development dependency.
If you need embedded engineering capacity alongside the codebase delivery, that can be scoped separately. The architecture review is the right place to discuss it.
No cost, no commitment. Bring your stack, your team shape, and the questions that are blocking the decision.