SellUp · prepared 3 September 2026

CollabSuite - SellUp

Proposal Package
Project
Technical SEO & Indexing
Site
mkt.sellup.com.sg
Scope from
Your Developer Implementation Brief
Prepared
3 September 2026

Thank you for getting in touch. What follows is our reading of the Developer Implementation Brief you sent us.

We took each requirement in it, checked what your site does today against what the brief asks for, and worked out what it would take to close the gap. That comes to five documents and three separate estimates, with one measured scan sitting behind all of them. Start with the proposal - everything else is here so that any figure in it can be traced back to the evidence it came from.

Where to start
Read the proposal first. It runs to nine parts in plain language, with the technical detail moved into clearly marked asides rather than removed. It is written for the person making the decision, not for a specialist.
What the work comes to
The engagement on mkt.sellup.com.sg is 48–79 hours. Of that, 34–55 hours we can commit to today with nothing further needed from you. The remaining 14–24 hours waits on a single decision about access, and if you decline it the engagement simply stands at the smaller figure.
What sits outside that figure
Two further pieces of work are quoted on their own. A portal SEO module comes to 57–97 hours, and a search growth programme is broken into four estimates you can agree to one at a time (24–40, 52–92, 37–63 and 11–18 hours). Each is a separate agreement, and each can be declined without touching the others. None of these three totals is ever added to another.
Why you can check every number
Twelve of our claims were measured directly against your live site, with a crawl of 451 URLs sitting behind them. Where the crawl contradicted us, we corrected our own finding rather than the page - one was withdrawn outright, and the discovery scan says which and why.
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

Send these two

Same numbers, two languages
01
Proposal - for the person making the decision
Nine parts. No jargon in the body; the technical detail is demoted into visibly-secondary "for your developer" asides rather than deleted. Carries the three options, twelve checks you can run yourself, eight things we are not doing, and the one outcome nobody can honestly promise.
9 partsView detail 02
Delivery view - for your developer or CTO to audit
Eleven parts. The same twelve work items split by discipline, the dependency register, the milestone roll-up, and the factors that would move the number - each marked according to whether we measured it or are assuming it. Offer this for technical review before signing, not after.
11 partsView detail

The evidence behind both

read it if a number looks wrong
03
Discovery scan - 451 URLs, 27 issue types
Six parts reading a full crawl and our own request-level scan. It is a detail page behind the other two, not a third proposal - the headline figure does not move on it, and one part explains why not. It also records a finding we withdrew: our own V9 was measured with an invented stock code, and with real values the behaviour is correct on all 133 cases the crawl found.
6 partsView detail

Separate agreements - outside the engagement total

Never added in
04
Portal SEO module - twelve mockup screens
A product design for an SEO module inside your own portal, so your team manages titles, descriptions, canonicals and schema without a developer. The SEO analysis dashboard, seven content-type list screens and three detail screens. The design already exists - the 57–97 h estimate was sized against these screens, which is why each of its eight items names the screens it came from.
57–97 hView detail 05
Growth programme - research, content, off-page, measurement
Six parts, and four separate estimates - research (24–40 h), content (52–92 h), off-page (37–63 h) and measurement (11–18 h) - each sized, footed and agreed on its own, exactly as the portal module is. None of it is in your brief - that is an engineering spec for one property, this is research, content and earned media. Five of its fourteen items are priced per unit, so you set the volumes and the total follows arithmetically. Includes a 58-point ecommerce SEO checklist with the seventeen items our scans already verified as done, and the evidence for each.
4 estimatesView detail

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.

And one page that is not a document

the only page carrying money
-
The team and the rate
Who does the work and what it costs: USD 20 per hour, flat across all six disciplines - back end, front end, QA, research, content and outreach. Every figure on it is an hour band × 20 and nothing else. Kept off the five documents on purpose - they carry hours only, so the rate can be discussed without reopening the scope.
Has pricesView detail

How payment works

7 milestones · 50 / 50 each
How payment works on every milestone A milestone runs from kick-off through delivery to sign-off. Half its agreed value is invoiced when it begins and the other half when it is signed off. The same pattern applies to all 4 engagement milestones and all 3 portal-module milestones; nothing is invoiced part-way through one. START Milestone begins scope agreed WORK The milestone is delivered nothing invoiced mid-way ACCEPT Milestone signed off you accept the deliverable 50% invoiced on kick-off 50% invoiced on sign-off APPLIES TO Engagement · 4 milestones Portal module · 3 milestones Each half is of that milestone’s own agreed value
A deposit on every milestone, not one deposit for the whole engagement. Each milestone is invoiced in two equal halves - 50% when it begins and 50% when you sign it off - and the percentages are of that milestone’s own agreed value, not of the total. The engagement has 4 milestones and the portal module 3; all of them are invoiced this way. Nothing is invoiced part-way through a milestone.