Fixed-scope builds for listing sites. Fields, filters and review rules are defined first, so the directory stays useful after launch.
Take one, two or all three. Each is quoted on its own, so nothing is bundled that you did not ask for.
A quote without these numbers is a guess. They are agreed in writing, and then the build follows them.
Every field a listing has, its type, and whether it is required.
How many listings at launch, and where they come from.
Which fields become filters, and how many in total.
Who can submit, what gets reviewed and what gets rejected.
The format and condition of the data you already have.
Where it runs, and how ownership passes to you.
You own the listings, the content and the data model. At handover you get a full export in CSV and JSON, and nothing in the build depends on staying with TopDown.
No. Without fields, volume and filter count, any number would be invented. Once those are written down, a fixed quote follows.
No. Maintenance has a monthly cap on updates and reviews, agreed in the quote. Work beyond the cap is discussed before it happens.
Yes. You own the data and receive a full export at handover. Nothing is held back.
A build includes launch checks on mobile and desktop. Separate testing later would go through the one-time App Check or the monthly testing plan, both described on the testing page and both not yet open.
Prepare a project brief in your browser with your fields, rough listing volume and filters. Nothing is sent.