In this Article
- The Genesis of a Perth-Based Survey Platform
- The Challenge: Standing Out in a Crowded Market
- The Solution: Pioneering Comparative Benchmarking
- Execution: From Private Beta to Public Launch
- Output Strategy: Making Data Digestible
- Results and Lessons for SaaS Founders
The Genesis of a Perth-Based Survey Platform
Perth does not give startup founders the luxury of pretending the market will find them.
That constraint shaped the early thinking behind Floq, the survey platform started by Jonah Cacioppe and Michael Kruger. The first product conversations were not about building another form builder. They were about whether a small Western Australian team could make survey data more useful at the exact moment product teams were drowning in feedback but short on interpretation.
According to project records, the initial scoping meetings ran from January 10 to February 3, 2022. The founders reviewed local market conditions in Western Australia before committing to a narrow product scope: actionable outputs first, basic collection second. That order matters. Most survey products start with the question interface and treat reporting as the back room. Floq started closer to the boardroom question: what will a product manager do with this once the answers arrive?
Why early 2022 mattered
The Australian startup scene was active, but not frictionless. Startup activity tracked through 14 public filings in Q4 2021 gave the founders a live read on capital movement, product appetite, and the kinds of teams still spending on customer insight. It was enough signal to move, not enough to get careless.
The early product thesis was blunt: survey software had become easy to launch and hard to differentiate. If Floq was going to matter, it needed to turn answers into judgement.
Main Point: The founding decision was not “build surveys.” It was “make survey results easier to act on.” That distinction became the spine of the product.
The Challenge: Standing Out in a Crowded Market
SurveyMonkey sat over the category like weather. Every founder building in surveys had to account for it, along with a long tail of specialist tools that promised faster forms, prettier templates, or cheaper response collection.
The Floq team reviewed 23 publicly documented survey platforms active in 2021. The pattern was hard to miss: plenty of tools could collect responses and export lists. Far fewer helped a UX researcher understand whether a score was strong, weak, normal, or worrying in context.
The common mistake: competing on feature volume
A young SaaS company can burn months trying to match the incumbent checkbox by checkbox. More templates. More question types. More export formats. That path looks disciplined on a roadmap and feels thin in the hands of users.
The root cause is usually fear. If a large competitor has a feature, the smaller team assumes buyers will punish them for not having it. In practice, product teams do not buy research tools because they admire the settings menu. They buy them because the next design decision is stuck.
Feedback sessions with 7 product teams over a 4-week window ending March 2022 made that clear. The pain was not response collection. The pain was interpretation.
- UX researchers needed a way to defend findings beyond “users said this.”
- Product managers needed signals they could take into prioritisation meetings.
- Founders needed to see whether a satisfaction score was meaningfully different from peers.
Caution: A raw export can look objective while hiding the real issue. In 2021 pilots, raw export tools failed to surface regional satisfaction drops below 3.2 on 5-point scales.
The Solution: Pioneering Comparative Benchmarking
Comparative benchmarking became the product’s centre of gravity because it answered the question raw data avoids: compared with what?
In survey work, a score without reference can be dangerously persuasive. A 3.8 rating might look healthy until it sits beside a stronger category benchmark. A complaint theme might look isolated until the same pattern appears across similar users, segments, or regions. Floq’s bet was that comparison layers would make research outputs more useful for product teams who needed to move from feedback to decision.
How the comparison layer changed the value of a survey
The feature choice came after mapping raw survey outputs against available industry reference sets. The benchmark dataset assembled from March 15 to April 22, 2022 included 1,800 responses. That dataset did not magically make every conclusion reliable, and it was not meant to. It gave the product a practical reference layer for continuous feedback loops.
There was also a guardrail: benchmark references required a minimum of 150 responses per category before comparison reports activated. That floor matters because thin categories can make normal variance look like insight.
Once the team treated benchmarking as the core feature, the survey itself became lighter. Pulse surveys, set at 14-day intervals for pilot users, fit the job better than heavy quarterly research cycles. They made it easier to watch sentiment move without asking users to complete another long diagnostic every time a product changed.
Expert Tip: Use pulse surveys when the product question changes quickly. Use deeper surveys when the business question needs explanation, segmentation, or qualitative follow-up.
The trade-off is real. Pulse surveys reduce friction, but they can decay if users do not see relevance. Continuous pulse formats showed 11-day response decay when deployed without benchmarking anchors. That is the quiet lesson: cadence alone does not create engagement. The feedback loop has to feel worth the interruption.
Execution: From Private Beta to Public Launch
The private beta opened on February 28, 2022 with 42 invited accounts. That is a useful size for early SaaS: big enough to expose rough edges, small enough that the team can still read the room.
The first 18 days were about stability fixes, not grand strategy. Login flows, report generation, survey completion paths, and usage logging all had to behave before the founders could learn anything meaningful from product behaviour. Early adopters are generous, but they are not infinite. If the basics wobble, their feedback quickly turns into bug triage.
Three release passes, then the public door opened
The rollout followed a practical sequence:
- Private access: Invite a contained Australian cohort and watch where the product breaks under real use.
- Usage-led adjustment: Prioritise fixes from usage logs, not the loudest hypothetical roadmap debate.
- Incremental release: Ship three iterative releases before widening access.
The public launch executed on May 19, 2022. By then, the product was not finished in the romantic sense. SaaS never is. But it had moved past the fragile stage where every new user introduced a new emergency.
One operational choice deserves attention: Western Australia-based development continued, with distributed review cycles every 21 days. That model gave the team a steady rhythm without pretending everyone needed to sit in the same room to make a useful product.
Output Strategy: Making Data Digestible
Here is where Floq’s case becomes especially relevant for SaaS founders outside the survey category: the output format can be the product.
Spreadsheets are useful, but they rarely win stakeholder support on their own. A UX researcher can spend hours cleaning exports, building charts, and translating findings into a format a product lead or executive team will read. That manual interpretation tax makes research easier to ignore.
Two valid output paths
The team looked at two approaches. The first was familiar: give users clean exports and let them shape the narrative. The second was more opinionated: produce automated visual summaries and structured reports that carried the finding, the comparison, and the likely implication together.
The export-first path gives sophisticated teams maximum control. It also assumes they have time. The automated-report path reduces flexibility but improves speed, especially when a product team needs to secure stakeholder buy-in for UX improvements before a sprint planning session or roadmap review.
Reporting formats were chosen after testing export options against stakeholder review cycles. White paper generation was tested on 9 sample datasets during April 2022. Visual summary templates were finalised after 5 internal review rounds.
- White papers helped package findings for senior decision-makers.
- Visual summaries made satisfaction gaps and benchmark comparisons easier to scan.
- Structured reporting reduced the chance that useful feedback stayed buried in a CSV file.
The recommendation is not to kill exports. Keep them. But do not mistake an export for an outcome. If the customer has to do all the interpretive labour after using the product, the product has stopped too early.
Results and Lessons for SaaS Founders
The launch did what an early launch should do: it created direct conversations. Coverage around the May 19, 2022 public release generated 31 direct inquiries in the first 10 days. For a Perth-based software company with a specific product wedge, that was a useful signal.
The more important result was strategic. Post-launch review confirmed that niche positioning around benchmarking reduced direct feature overlap with larger survey tools. Floq did not need to beat SurveyMonkey at being SurveyMonkey. It needed to own a sharper job for UX researchers and product teams: turn response data into comparative insight.
What founders can take from the case
- Pick a wedge that changes the buying conversation. Comparative benchmarking shifted the discussion from survey creation to decision quality.
- Let constraints do some work. Building from Western Australia forced a clearer point of view, not a weaker one.
- Protect the trust layer. Minimum response thresholds, such as 150 responses per category, prevent thin benchmarks from becoming decorative claims.
- Design the output, not just the input. A better questionnaire is useful. A better decision artefact is harder to ignore.
There is a broader lesson here for Australian SaaS founders. A global competitor can be too large to copy and still leave valuable work unfinished. The opportunity is often not in building every feature the incumbent has. It is in finding the moment where users still feel alone with the data.
Floq’s early case shows a practical path: study the category, find the interpretive gap, build the comparison layer, and make the output usable by people who were not in the research session. That is not a slogan. It is the work.
