Project Roadmap: From First Brief to Daily Work
A predictable launch requires clear responsibilities. You always know what is being done, what your team needs to provide, and how each milestone is verified.
Target timeframe for standard OneWindow packages is 7–14 business days. The clock begins once all required materials, domain access, and price lists are provided.
The 8-Stage Implementation Flow
| Stage | What You (the Client) Do | What 1it.pro Does | Deliverable / Output | Milestone Completion Criteria |
|---|---|---|---|---|
| 1. Define Problem & Goal | Describe your business model, customer pain points, target geography, and assign a primary project owner. | Recommends the appropriate solution format (OneWindow package, CRM, AI pilot, or private system). | Agreed preliminary scenario. | Clear understanding of deliverables and exclusions. |
| 2. Agree Scope & Package | Choose package (Start / Business / Pro), confirm required languages, channels, and approve budget. | Prepares formal scope of work, timeline dependencies, and invoice. | Confirmed Scope of Work & Invoice. | Agreed package with no ambiguity on what is included. |
| 3. Prepare Materials | Provide texts, logo, price list, hours, staff contacts, and domain/notification access (see Materials & Access). | Audits completeness of assets, flags missing items, and prepares staging environment. | Complete asset kit & verified accesses. | Client project owner confirms all provided data is accurate. |
| 4. Configure & Test Build | Answers clarifying questions and approves staging preview. | Builds website, admin panel, CRM pipeline, and notification channels on staging environment. | Working staging test installation. | Primary scenario (page display + test form) works end-to-end. |
| 5. Acceptance & Training | Tests sample lead submission, verifies admin panel login, and checks content editing. | Conducts demonstration walkthrough, corrects any scope deviations, and delivers admin credentials. | Signed acceptance checklist. | Client team successfully performs sample content edit and verifies test lead. |
| 6. Production Launch | Confirms launch date and assigns staff to monitor notifications. | Points domain DNS to production server, issues SSL certificate, and sends live test enquiry. | Live website and operational system. | Live test enquiry arrives in Telegram and CRM successfully. |
| 7. Daily Operations | Updates prices, hours, and text independently; processes incoming enquiries and tracks next actions in CRM. | Maintains European cloud hosting, daily backups, security patching, and uptime monitoring. | Stable daily business process. | Team manages enquiries without developer intervention. |
| 8. Modifications & Offboarding | Submits change requests for new custom modules or requests data export upon contract completion. | Estimates custom changes or executes secure data handover per policy. | Extended scope or clean handover. | Data, backups, and credentials securely transferred to client. |
What Determines the Launch Timeline?
- Content Readiness: The 7–14 day launch target begins only after all mandatory texts, prices, and assets are submitted. Delays in providing materials pause the launch countdown.
- Domain & DNS Access: If your domain is held at an external registrar, providing DNS management access promptly prevents propagation delays.
- Scope Discipline: Standard packages are launched with the agreed feature set. New custom features requested mid-flight are scheduled for Stage 8 as an enhancement phase.
Transparent tracking
You don't need to guess where your project stands. Your project lead communicates milestones directly in our shared channel, and you can test the staging system before anything goes live.
Next step: Review the Acceptance and Handover Checklist to see how completion is verified.