Report — 2026-09-19

Do

• Write a continuity-of-personnel clause into the SOW: the PM and tech lead are named, cannot be swapped without the client's written consent, and any approved change carries a two-week paid overlap handover.

  PM churn is the single mechanism by which a 4.6-rated firm produces catastrophic individual engagements — the client loses the person who held the context and never recovers it.

  Appinventiv (Clutch 4.6/5, 90 reviews): Review Highlights name 'changes in project managers' among recurring project-management challenges; one verbatim review says the assigned PM 'rarely delivered fully functional products/sprints'.

• Tie every payment milestone to an accepted working increment — a demo on the client's own environment plus a signed acceptance checklist — and never to elapsed calendar time or invoicing intervals.

  When money is pegged to time rather than accepted software, the delivery team's incentive is to report progress, not ship it, and the client discovers the gap only at the end.

  Appinventiv: a client wrote that the PM was 'essentially stringing us along on issues and progress while pushing to ensure payment intervals were met and up to date from us,' with 'virtually no part of our technology' working properly.

• Run a formal remote-transition protocol the week any on-site or co-located phase ends: recorded daily demo, weekly build deployed to the client's environment, and a written burn-down of open defects by severity.

  Distance is when delivery quality silently decays, and MENA/GCC deals frequently start with an on-site kickoff followed by months of remote work — exactly the shape that failed here.

  Appinventiv: 'Our experience when working on site in person with the team was an overall success. Once we flew back to America and left them to continue in India is when the issues starting arising.'

• Publish a working-calendar annex with every proposal: the Egyptian Fri-Sat weekend stated up front, guaranteed overlap hours per client region (EU, Gulf, US East, US Pacific), a named Friday on-call engineer, and the escalation path outside those hours.

  The calendar mismatch is a structural fact of Egyptian delivery — disclosed early it is a logistics detail, discovered late it becomes the client's schedule complaint on a public profile.

  BLUE DEVELOPMENTS (Clutch 5.0/5, 6 reviews) loses its only rating points on Schedule (4.6) with the verbatim cause: 'Time difference made things a little difficult as we are on PST and Blue Developments is on Egypt time. Also Egypt's weekend is Fri and Sat.'

• Own the check-in calendar on Devya's side: a standing triage slot for bugs and open issues, booked by Devya with an agenda, running whether or not the client asks for it.

  Being responsive when contacted is not project management; clients read an unbooked calendar as them having to drive the engagement.

  BLUE DEVELOPMENTS: the sole improvement request in a 5.0-rated review is 'Proactively schedule check-ins to go over bugs and issues,' and Clutch's own highlight reads 'Proactive Communication Needs Improvement.'

• End week one with a restate-back specification: Devya rewrites the requirements in its own words with assumptions, exclusions and open questions listed, and the client signs that document before any production code is written.

  Requirement misunderstanding at the start is cheap to fix in week one and expensive in month three; a signed restatement also converts later change requests into billable scope rather than arguments.

  RIKSOF (Clutch 4.7/5, 13 reviews): Review Highlights record that 'some clients experienced initial challenges with RIKSOF's understanding of project requirements,' and a reviewer's advice is 'As long as clients provide clear requirements, RIKSOF's developers are capable of quickly getting up to speed.'

• Give the client named, direct access to the engineers building their product — shared channel, engineers present in demos — with the PM coordinating rather than intermediating.

  A PM-only interface slows technical decisions and makes clients suspect they are being managed instead of informed; it is a complaint that survives even on well-rated firms.

  RIKSOF: a client who rated the work highly still asked for 'a little more communication with the client directly'; another describes an arrangement where 'the client never had direct involvement with RIKSOF, always working through me.'

• Attach a priced architect-advisory retainer to every embedded-squad or staff-augmentation deal — stacked hours for architecture review, tech-debt strategy, security posture and build/buy decisions, delivered by a named senior.

  Pure capacity is the commodity end of the market; the advisory layer is what the biggest staff-aug players are being asked for and not delivering, and it is where margin and retention live.

  Vention (Clutch 4.9/5, 102 reviews, $50-99/hr): the concrete improvement a client names is that Vention 'could enhance its services by offering more expert consultancy and advisory support in specialized areas.'