SellUp · prepared 3 September 2026

Everything we have prepared for SellUp

Five documents, three separate estimates, one measured scan behind all of it. Start with the proposal; the rest is there so every number in it can be checked.

Start here
The proposal — nine parts, plain language, no jargon in the body. It is the document written to be read by someone who does not work in search.
The work itself
48–79 hours on mkt.sellup.com.sg — of which 34–55 h we can commit to today and 14–24 h depends on one access decision.
Two more, kept apart
A portal SEO module at 57–97 h, and a search growth programme offered as four separately-agreeable estimates (24–40 · 52–92 · 37–63 · 11–18 h). Both are separate agreements. None of these three totals is ever added to another.
Why you can check it
Twelve claims were measured against your live site, and a full crawl of 451 URLs sits behind them. Where the crawl disagreed with us, we changed our own finding rather than the page.
Payment
A deposit on every milestone — not once per engagement. Each milestone is invoiced in two equal halves: 50% on kick-off and 50% on sign-off. The engagement has four milestones and the portal module three, each invoiced the same way. Percentages are of that milestone's own agreed value.
5 documents3 estimates · never summed48–79 h engagement451 URLs crawled
Documents5
Engagement48–79 h
Portal module57–97 h
Growth · 4 estimates124–213 h
Measured claims12
URLs crawled451
Mockup screens12
Findings withdrawn1

How the five documents relate

2 audiences · 1 evidence base · 2 separate agreements
What SellUp receives, and which documents sit outside the engagement total Map of the five deliverables. One discovery scan supplies the evidence for two documents that carry identical numbers in different languages: a proposal for a non-technical decision-maker and a delivery view a developer audits. A separate dashed region holds the portal SEO module and the growth programme, which are agreed independently and are never added into the 48 to 79 hour engagement total. THE ENGAGEMENT · 48–79 H SEPARATE AGREEMENTS · NEVER ADDED IN SAME NUMBERS EVIDENCE Discovery scan 451 URLs · 27 issue types SEND THIS Proposal 9 parts · plain language TECHNICAL Delivery view 11 parts · full trace SellUp decision-maker non-technical reader Developer / CTO audits the numbers SEPARATE Portal SEO module 57–97 h · 12 mockup screens SEPARATE Growth programme 4 separate estimates · 124–213 h all in LEGEND who each document is written for supplies the measured evidence the document you send to SellUp separate agreement, outside the total
The proposal and the delivery view carry identical numbers — only the language differs, so a non-technical reader and a developer can be given the same estimate without either being handed the wrong document. The two dashed items are agreed separately and are never added into the 48–79 h.

What each document is

In the order we would send them. Every band traces back to a work item, and every work item to a clause in your brief.

5 documents

How the work would run — kick-off to handover

4 stages · 4 slots · 48–79 h
Engagement stages, kick-off to handover Stage framework for the SellUp technical SEO engagement. Four milestones run left to right, and each is described by the same four slots: what SellUp provides, what the delivery team does, the gate that must pass before the stage can be left, and what SellUp receives. Milestone one is highlighted because its gate re-confirms the effort estimate before any production change. Two inputs are marked as dependent on the commercial deal: access to the Express sitemap service and access to the stock data. M1 DISCOVERY 8-12 h M2 CANONICALS 12-20 h M3 STORE + LINKS 17-30 h M4 SCHEMA + QA 11-17 h STAGE → SLOT ↓ YOU GIVE WE DO GATE YOU GET KICK-OFF HANDOVER SU Repo, staging, config + a named approver SU DEAL Signed rule set Express service access SU DEAL Stock and dealer data + dealer copy SU Search Console access full-user, not view-only WE Inspect both codebases full crawl · access list WE Canonicals + parameters 301 · 404 · 410 · sitemap WE Store SSR + fallback 324 URLs · internal links WE Product + store schema staged release GO ESTIMATE RE-CONFIRMED BEFORE ANY PRODUCTION CHANGE GO Automated tests pass ROUTE · CANONICAL · SITEMAP GO Before / after crawl EVERY CLASS OF CHANGE GO 38 URLs × 7 checks 7 FIELDS EACH · NO BLANKS YG Discovery report approved URL rules YG Sitemap incl. store pages test suite, yours to keep YG Mister Mobile repaired crawl evidence YG Evidence pack + handover GSC validation started LEGEND STAGES M1 8-12 h M2 12-20 h M3 17-30 h M4 11-17 h SLOTS YOU GIVE = what SellUp provides │ WE DO = the work │ GATE = what must pass before the stage is left │ YOU GET = the deliverable, checkable DEPENDS DEAL = needs access we do not yet have — the Express sitemap service (M2) or the stock data (M3). Decline both and the engagement is 34–55 h, not 48–79 h. FLOW leaves the re-confirm gate — nothing touches production before it stage handoff — a stage is left through its gate, never around it
Four stages, and every one answers the same four questions: what SellUp gives, what we do, what must pass before the stage is left, and what you get to keep. Nothing touches your live site until stage 1’s gate has re-confirmed the estimate — the highlighted cell. The two DEAL cells need access we do not yet have; decline both and the engagement is 34–55 h, not 48–79 h. Both the proposal and the delivery view carry these four stages in more detail.