# Marcus Reyes, Head of Growth at Fieldvault — read of automated-review-collection, June 9 2026 > 8 years in SaaS, currently 18 months into building a B2B field service management platform, ~40 customers, $14k MRR, and a G2 profile with exactly one review that my co-founder wrote. ## How I got here A warm prospect last Tuesday told me, over Zoom, that he had Googled us before the call and "couldn't find much." He meant reviews. I said "yeah working on that" and then felt embarrassed. Typed "how to get G2 reviews enterprise customers" that same night. This came up on page 2. Clicked it expecting a listicle. Got a product page instead. ## What I clicked first The subheadline got me: "Collect reviews on your timeline, not theirs." That's a real thing. The actual pain is that my customers are all mid-market operations teams who go live six months after signing and then are too buried in the rollout to write a 4-sentence G2 blurb. So "Ask too early, and customers haven't experienced enough value. Ask too late, and the moment of enthusiasm has passed." That sentence is accurate. I've done both of those things this quarter. ## Where I paused The lifecycle trigger list: "first successful task completed, first week in production, recurring revenue threshold hit, or days since go-live." I stopped there because I wanted to know whose definition of "first successful task completed" this is. My platform knows when a field tech closes a job. Does this tool know that? Or is it watching Stripe for a charge? There's a huge gap between those two things. The page doesn't explain it, it just says "real lifecycle events" and moves on. ## What I distrusted "Typical result: 40-60% higher completion rates than manual asks. 3-5 new reviews per month on autopilot." I kept scrolling to find a source for that. Then I hit this near the bottom: "Honest disclosure: we don't have live customers on this idea yet." OK so those numbers are made up. Or they're benchmarks borrowed from some other context. The page presents them as results before disclosing there are no results. That's not a good order of operations. I don't think it's intentionally deceptive but it's sloppy enough to make me doubt the whole framing. Also: "30-second setup" is in the same sentence as "Connect to Stripe," "Connect to HubSpot or Salesforce," and "Connect to your custom database via API." Those are not 30-second things. Not even close. ## What would convince me One real founder, named, with their actual product, saying something like "we went from 2 G2 reviews in our first year to 11 in 90 days." Not a percentage lift. An actual count on a real platform from a real company I can look up. If it's a niche B2B product even better. I don't need a household name. I need someone in a similar boat. Also: show me what the Slack DM actually looks like when it goes to a customer. Show me the email template. I want to see the thing touching my customers before I hand over access to my HubSpot. ## What I'd ask in an email reply 1. The page says "first successful task completed" is a trigger. How does the system know what counts as a success in my product? Is that a webhook I configure, a custom event I send, or does it only work off Stripe/HubSpot signals? 2. You say "no live customers yet." Are you actively building this, or is this a concept you're validating before building? I want to know if I'd be customer zero or if there's something running I could actually try. 3. What happens when a customer leaves a negative review through one of these workflows? Is there any catch or review before it posts, or does it go straight to G2? ## Verdict: on-the-fence The problem description is the best part of this page and it's accurate. But the product is not demonstrably real yet, and the stat that should build trust ("40-60% higher completion rates") appears before the disclosure that there are no customers. If someone emailed me with a live demo environment and a single real case, I'd take a call. --- *Memo by skeptic persona, generated 2026-06-09. Studio breaks own self-grading loop.*