Report — 2026-08-25

Do

• Tie every milestone invoice to named, verifiable deliverables — a tagged repo state, a deployed build the client can open, a demo recording — and attach that proof to the invoice itself, never to hours logged.

  The fastest way a strong profile turns toxic is a payment dispute where the vendor can't show what was delivered; proof-per-invoice makes the dispute impossible to start.

  Cubix's 0.5★ Clutch review: client paid $9,250, says milestone 2 deliverables 'were never delivered at all', and that Cubix deflected proof-of-delivery questions 'with references to hours worked' — dispute now filed with the Florida AG, FDACS, FTC and BBB, publicly readable on a 4.8/56 profile.

• Make PM continuity a contractual commitment: name the PM in the SOW, and if a change is unavoidable, run a one-week paid-by-Devya overlap plus a written state-of-project handover the client signs off.

  PM churn is the single most repeated complaint across every tier of today's pool — it converts healthy projects into delay-and-miscommunication spirals.

  Cubix Clutch highlights: 'challenges with communication, particularly during project manager transitions'; Hyperlink review: 'changed managers two times, delaying the development'; Folio3 reviews note PM turnover 'occasionally disrupts workflows'.

• Give every client a live milestone dashboard — planned vs. actual per milestone, RAG status, and a named owner for each slipping item — updated weekly without being asked.

  The catastrophic reviews in today's pool are not about bad code; they are about clients discovering drift late and alone.

  Hyperlink InfoSystem's May 2026 1.0★ (Dubai sports platform, $50k–$200k band): 'the project lacked clear accountability, structured milestone tracking, and proactive escalation of delays' — 60% complete after two years.

• Enforce shippable increments on a fixed clock: no engagement goes more than 8–10 weeks without a release the client can actually use, and any phase that misses two consecutive increments triggers a written re-plan.

  Two-year projects that are '60% complete' happen one quiet fortnight at a time; a hard increment cadence makes drift visible at week 10, not month 20.

  Hyperlink InfoSystem 1.0★: two years elapsed, app 'minimally usable', client built workarounds around the vendor's shortcomings.

• Concentrate all review equity in one Clutch profile and harvest a verified review at every project close — target 15–20 GCC-named reviews within a year.

  The proof bar in Devya's home market is startlingly low: Egypt's #1-ranked shop has 38 reviews, and the biggest legacy name has none — a disciplined review pipeline can put Devya on the first page of Egypt rankings in quarters, not years.

  Blink22 leads Egypt with just 4.9/5 (38 reviews); ITWorx has zero client reviews on Clutch and GoodFirms; Folio3 splits its equity across profiles (main shows 4.9/6 while aggregates claim ~50+); Nile Bits shows one review from 2020.

• Run QA as a visible workstream from sprint 1 — QA engineer named in the plan, test evidence attached to each release note — not as a phase bolted on before launch.

  Even the best-reviewed shop in today's pool has exactly one recurring criticism, and it's early-project QA; making QA visible from day one removes the one dent in an otherwise clean profile.

  Blink22's Clutch highlights (4.9/5): 'initial QA efforts were noted as slightly lacking, though improvements were made over the course of projects' — the sole negative theme on the profile.

• Productize a startup/SMB entry tier — a fixed-price, fixed-scope first engagement with explicit flexibility on payment scheduling — and say so on the website.

  Flexibility toward smaller budgets is a named, repeated praise theme that turns first projects into long relationships, and it feeds the review pipeline with grateful early-stage founders.

  Cubix's highlights credit 'flexible pricing and accommodating budgets' for nonprofits/startups; Blink22 scores Cost 4.8 with 'high value for cost' the top-mentioned theme; Hyperlink wins deals at the $10k entry band on 'competitive pricing and value'.

• Write scope and milestone changes as signed change orders before work shifts — and audit each project monthly for undocumented drift between contract and reality.

  When a dispute comes, the contract you didn't follow becomes the other side's best exhibit; Devya's paper trail must match its own contract mechanics.

  Cubix's 0.5★ reviewer quotes Cubix's own contract against it: 'any changes to scope or milestones should be documented in a written Change Order as required by their own contract.'