TecnoStack
Start a projectالعربية

Silent video with on-screen text. The transcript below repeats every screen and describes what it shows.

  1. 0:00–0:06

    Project brief A • Send one brief to everyone • Same version for all • Assumptions in writing

    The "Project brief A" badge stays fixed in its lane. A brief sheet, drawn like the badge's own tile, stands first, with three blank company cards after it. Cyan routes trace from the sheet to each card and three identical copies of the brief slide along them; "Same version for all" appears. Each card then sends out one blank assumptions sheet with a dashed outline, and its blank lines are written in; "Assumptions in writing" appears. No company is named or rated.

  2. 0:06–0:12

    Project brief A • Ask for evidence you can check • References you choose • The named team • Reference list • You choose whom to call • When a deadline slipped

    The badge stays fixed. The article's references figure enters: a "Reference list" rack of identical blank client cards whose fourth card sits in its slot. That card slides out of the rack along a cyan pointer that traces after it, comes to rest outlined in cyan and is labelled "You choose whom to call"; "References you choose" appears. An empty glass speech bubble then opens beside the card under "When a deadline slipped" and stays empty. A small team panel arrives with three faceless members over blank name bars: "The named team".

  3. 0:12–0:18

    Project brief A • Compare scope before price • Included, excluded, assumed • Price follows scope

    The badge stays fixed. The brief's feature list stands beside two proposal columns whose rows line up with it. Row by row, each feature gains one of three empty markers in both columns, a ring, a square or a diamond, for included, excluded or assumed; "Included, excluded, assumed" appears. Dashed routes then run from both columns to two empty total slots, which are outlined and stay empty: "Price follows scope". No totals, prices or counts appear.

  4. 0:18–0:24

    Project brief A • Write acceptance into the contract • Milestones you can review • Ownership and licences

    The badge stays fixed. A contract sheet with seven blank clause rows docks into place. One row is outlined in cyan and a route traces from it to three empty review screens joined by a dashed track: "Milestones you can review". A second row is outlined and a route traces to two separate blocks, one solid and one glass: "Ownership and licences". Nothing is written on the sheet.

  5. 0:24–0:30

    Project brief A • Test the handover • Receiving team builds alone • Support agreed before launch • Outgoing team access • Accounts in your name • Revoked after transition • Rotated credentials

    The badge stays fixed. The article's access figure enters: the "Outgoing team access" key card, a dashed link from it to the plain "Accounts in your name" block, and a glass key outline for "Rotated credentials". "Receiving team builds alone" appears. The dashed link then loses its middle, leaving two round cut ends, and "Revoked after transition" appears by the break. A cyan arrow traces from the block to the fresh key, and "Support agreed before launch" closes the scene; nothing else changes.

An illustrative project brief goes to every shortlisted company, then evidence, references, scope, contract and a tested handover decide; no company is rated or chosen.

Read the article: How to Choose a Software Development Company in the GCC