1,009 views
Here’s where things stand with Reporting & Analytics Dashboard as we keep building out OPERATE — an honest snapshot rather than a polished announcement, since I think pet business owners deciding whether to trust a piece of software deserve the real picture, not just the highlight reel.
What’s live today
Reporting & Analytics Dashboard pulls bookings, revenue, and client activity into one dashboard instead of manual spreadsheet tallies, and that core functionality is already in place for pet businesses using OPERATE. Owners can see booking trends over time, a revenue breakdown by service type, and a simple view of active versus inactive clients without touching a spreadsheet. This has been stable and in regular use for a meaningful stretch now, not something we shipped last week and are still nervous about.
What we’re refining
We’re actively taking feedback from working pet sitting and dog walking businesses and using it to sand down rough edges before we call any feature finished. Right now that means adjusting how trend comparisons are displayed based on requests for clearer week-over-week and month-over-month views, and working through requests for export options so owners can pull their data into whatever accounting software they already use.
None of this is a secret roadmap locked away somewhere — it’s genuinely shaped by what owners tell us is missing or confusing when they use the dashboard in a normal working week.
Why we build in the open
OPERATE is built by people who’ve actually run pet care businesses, so progress updates like this one are part of how we stay honest about what’s actually ready versus what’s still in progress. I think a lot of software marketing blurs this line deliberately — everything sounds “done” and “polished” in the announcement, and then users discover the rough edges themselves after they’ve already committed to the tool. We’d rather be upfront that a feature is genuinely solid but still evolving, because that’s a more accurate description of how good software actually gets built.
How this feature has changed since its initial release
Reporting & Analytics Dashboard has continued to evolve since its initial release, with refinements driven directly by how real pet businesses are actually using it day to day. We track usage patterns and support requests closely to catch friction points early, rather than waiting for a major version update to address them. A few concrete examples: we shifted emphasis away from single-day snapshots toward trend views after seeing that owners consistently cared more about direction than a single number, and we simplified the default view after watching new users get slightly overwhelmed by too many options presented at once.
What “actively refining” actually looks like week to week
This isn’t a vague commitment — it’s a specific, ongoing process. Every week, we review support tickets and direct feedback related to the dashboard, looking for patterns rather than reacting to every single individual request in isolation. If three different pet business owners independently ask for the same thing within a short window, that’s a much stronger signal than one person’s individual preference, and it moves up our priority list accordingly.
We also periodically reach out directly to a rotating group of active users and ask open-ended questions about what’s working and what isn’t, rather than only relying on people to proactively submit feedback. Some of the most useful insights have come from owners who wouldn’t have thought to file a formal request but had a clear opinion once asked directly.
If you’ve used this feature and have feedback
If you’ve used this feature and have feedback, that input directly shapes what gets prioritized next. This isn’t a formality — genuine changes to the dashboard have come directly from specific pieces of user feedback, not just internal assumptions about what “should” be useful. If something about the dashboard feels confusing, incomplete, or like it’s missing an obvious feature, that’s worth telling us, because it’s exactly the kind of input that shapes what we build next.
What’s coming next
The current priorities, based on what we’re hearing most consistently: better export options for accounting software integration, more granular per-sitter performance views for owners managing larger teams, and refined comparison views that make trend direction even clearer at a glance. None of these are locked commitments with hard deadlines — we’d rather ship something genuinely useful a bit later than rush a half-considered version out to hit an arbitrary date.
Questions we get asked about our update process
How often do you actually update this feature? Small refinements happen on a rolling basis, often every few weeks, based on the feedback patterns we’re seeing. Larger additions, like a new report view, happen less frequently but are still driven by the same feedback loop rather than an arbitrary release schedule.
Will updates ever break something that currently works? We test changes against real usage patterns before shipping, specifically to avoid this. If something ever does regress, we treat that as a priority fix, not something to quietly patch later.
Do you ever remove features based on low usage? Occasionally, yes. If a specific view or option genuinely isn’t being used and isn’t solving a real problem for anyone, we’d rather simplify the dashboard than leave clutter in place out of inertia.
How do you decide what to prioritize when multiple requests come in? Frequency matters — if the same request comes from multiple independent owners, it moves up the list. We also weigh how directly a request ties to the dashboard’s core purpose versus being a nice-to-have that would add complexity for a narrow use case.
A specific recent example
A handful of owners managing larger teams told us the current dashboard didn’t give them an easy way to compare performance across individual sitters, only aggregate totals for the whole business. That’s now on our near-term roadmap specifically because it came up independently from several owners with similar team sizes, not because it was an obvious gap we’d identified internally. This is a good example of the feedback loop actually working the way we intend it to.
What building this way actually costs us
Building this transparently and iteratively is slower than shipping a feature-complete version once and calling it done. It means occasionally telling users “that’s a good idea, it’s not built yet” rather than pretending every feature already does everything. I think that trade-off is worth it, because the alternative — overselling what a feature does today — erodes trust the first time an owner discovers the gap themselves. A pet business owner deciding whether to build their operations around OPERATE deserves an accurate picture of where things actually stand, not a more flattering one.
Why this matters more for software than most products
Unlike a physical product that ships in a fixed, final state, software that a business depends on daily needs to keep evolving alongside the business itself. A dashboard that was perfectly sufficient for a five-contractor operation may need additional depth once that same business grows to twenty-five contractors. Being upfront about ongoing development isn’t a weakness — it’s an honest acknowledgment that a tool meant to grow with a pet business has to keep growing itself.
How my own experience running Scritches informs this
Running a pet business that grew from a handful of contractors to 35 taught me firsthand that the tools I needed at five people weren’t the same tools I needed at twenty-five. What felt like plenty of dashboard detail early on became genuinely insufficient once the business had more moving parts to track. That personal experience is part of why we build OPERATE’s features to keep evolving rather than treating any version as a fixed, final state — because I know from direct experience that a growing pet business outgrows static tools faster than most owners expect going in.
It’s a lesson we’ve built directly into how OPERATE gets developed: assume today’s dashboard won’t be sufficient forever, and keep the feedback loop open so it doesn’t have to catch up all at once when a business’s needs finally outgrow it.
If you’re an OPERATE user reading this and wondering whether it’s worth submitting feedback that feels minor, it is. Some of the most impactful changes came from small, specific observations, not sweeping feature requests.
Send it through the app’s feedback channel or mention it during a support conversation — either route reaches the same place, and both get read by people actually building the feature, not routed into a queue that never gets reviewed.
We read every single one, even the ones that don’t turn into an immediate change, because patterns across many small pieces of feedback are exactly how we decide what to prioritize next.
That’s genuinely how this feature, and every other part of OPERATE, keeps getting better — not through a fixed roadmap decided once and executed blindly, but through an ongoing conversation with the people actually using it every day.
Want to see Reporting & Analytics Dashboard in action? Check out OPERATE — free forever.
