FlipStack

A few things to lock down

Hi Brett — thanks again for the detail in your last email. That cleared up the data side nicely: national coverage including WA, monthly updates, ~30-year sales/rental history, and the Property Profile API tiers.

Before we commit and start building, there are a couple of things we still need to pin down — mainly the sandbox and how your pricing maps to the way we'll actually use the data.

Quick context so the pricing questions make sense: FlipStack meters data usage — we pass data costs through to our users on a cost-plus basis, so we need a clear per-unit cost to build on. The sandbox is purely for our build and testing while we have no live users; once we open beta we move to paid, metered production.

— Luke, FlipStack · flipstack.com.au

Quick button for a fast answer, or the context box for anything that needs detail. When you're done, hit Submit answers at the bottom (or Export to PDF). Thank you.
Sandbox & path to production
1.Can you give us a sandbox / test key with real WA data so we can build and validate the full product end-to-end during development — at no cost while we have no live users?
Purely build and test — no live users, no resale yet. This is the thing that unblocks our build.
2.When we open beta we switch to paid, metered production. Can we move from the sandbox straight into live production without re-integrating — and what's the cleanest path you'd recommend from test → beta → production?
We want one integration that carries through from build to launch.
Commercial — so we can meter accurately
3.Your Property Profile tiers are by property count (e.g. up to 5,000 for $1,000). Is that 5,000 unique properties or total calls, does it reset monthly, and what's the cost once we exceed a tier?
We need the true marginal cost per property to set our cost-plus metering. If the same property is looked up twice, is that one unit or two?
4.Separately from property profiles, how is the comparable-sales search priced — the sold/rental research calls you flagged as higher-volume? Per call, tiered, or bundled, and at what unit rate?
This is our single most-used call (we pull comps around a subject property), so its unit cost drives our pricing more than anything else. On volume: expect modest at beta, scaling per user from there.
5.Your pricing so far covers the Property Profile API. How is everything else metered — suburb statistics / demographics / timeseries, the AVM, planning & hazard overlays, development applications / BCI, and listing media? Included in the property-profile allowance, bundled, or priced separately — and at what unit rate?
We use several of these (suburb data especially), so we need a unit cost on each class to meter it through to users.
6.What are the rate limits and any bulk allowances? (You referred these to commercials last time.)
Licensing & data rights
7.Does your licence permit a derived, resold product — where we transform and resurface your data inside a paid SaaS, and sell a derived report to our users?
This is fundamental to how our product works, so we'd want it confirmed in writing.
8.Does your licence allow us to cache responses server-side and retain derived signals over time?
We cache to manage cost and latency — and it affects how property counts above are tallied.
9.Are there attribution requirements, and on cancellation, what are we required to delete?
A couple of remaining details
10.How far back does your historical image archive go? For a typical WA property, roughly how many past listing campaigns carry photos?
We use historical listing imagery to understand a property's condition over time.
11.One technical detail: for comparable-sales search, what does the filters array support for geo selection — a radius around a point, a bounding box, or another method?
We pull comps around a subject property — happy for your team to field this one.
or email directly

Sent — thank you.

Your answers are on their way to the FlipStack team. Feel free to close this page.

FlipStack · flipstack.com.au · sent 23 Jun 2026