Kamero
The #1 AI-Powered Photo Sharing Platform.
I’m building [Kamero](https://kamero.ai/), an AI-powered event photo delivery platform, to solve a massive friction point in the event industry: the endless photo scroll.
Traditionally, photographers dump 5,000+ photos from a wedding or corporate event into a cloud drive link. Guests then have to manually hunt through folders just to find the three pictures they are actually in. It is a terrible user experience.
We wanted to fix this by treating the gallery as a searchable database, using the guest's face as the query. At [Kamero.ai](https://kamero.ai/), we built a custom AI facial recognition engine and live camera-to-cloud FTP sync so photos are matched and delivered to guests in real-time, using just a selfie, while the event is still happening.
Our biggest recent milestone: Launching dual-pricing.
We recently rolled out a dual-pricing model to fit completely different user segments, which has been a game-changer for our positioning:
* Pay-Per-Event (Based on photo count): Perfect for the casual searcher hosting a one-off corporate retreat or party. No hidden subscriptions.
* SaaS Subscriptions: Built for professional wedding photographers and event agencies who do high volume and need predictable, scaling costs.
Offering both options completely changed our sales conversations with larger B2B clients who hated unpredictable per-event costs, while still allowing us to capture one-off event planners.
My question for the community:
Have any other founders here successfully balanced a pay-as-you-go model alongside a recurring SaaS subscription? How do you keep the messaging clear on your landing page without confusing the user?
When we first built Kamero, our focus was simple: build a great AI face-search web gallery to deliver event photos instantly.
It worked well, but as we started talking to higher-end wedding studios and enterprise event organizers, we kept hitting a wall with brand perception:
"We love the AI face matching, but we don't want our luxury clients to see a third-party link. We want our own app icon on their home screen."
At first, we tried offering standard web white-labeling (custom subdomains and logos). But for high-end photography businesses, a web app still felt like a workaround. They wanted real mobile apps published under their own developer accounts on the App Store and Google Play Store.
The Pivot to Infrastructure-as-a-Service
Instead of trying to fight this objection, we leaned into it. Over the past few weeks, we automated our build and deployment pipeline:
Turnkey App Generation: We can now spin up a fully customized iOS and Android app with their studio branding, icons, and themes.
7-Day Delivery: We handle the end-to-end publishing directly into the client's Apple/Google developer accounts within a week.
Shared AI Core: Under the hood, all apps tap into the same real-time camera-to-cloud FTP sync and facial recognition engine.
What This Changed for Our Business
Higher Contract Value: Shifting from standard monthly subscriptions to dedicated custom app packages unlocked a completely new, high-intent tier of B2B buyers willing to pay upfront for infrastructure.
Near-Zero Churn: Once an agency has their own branded app live on their clients' phones, it becomes mission-critical software.
Clear Competitive Moat: While competitors offer gallery links, offering a native app in the App Store under the client's own brand is extremely difficult for most platforms to match.
My Question for Other B2B Founders:
If you sell SaaS, have you ever built custom/dedicated solutions (like white-label native apps or dedicated instances) for higher-tier clients? How did you balance keeping your core codebase maintainable without turning into a custom software agency?
Would love to hear how others manage white-label products at scale!
— Rishabh Thakrar, Founder of Kamero
3 Comments
The change in the B2B conversations is the interesting part here.
Since launching both models, have customers been naturally identifying which option fits them, or are you finding that you still have to explain the distinction during the sales conversation?
Hey Aryan, great question. It’s actually been a bit of both!
For the self-serve, pay-per-event side, customers naturally identify it themselves. A corporate HR manager hosting a one-off annual retreat doesn't want to talk to sales or be locked into a subscription. They just see the flat fee, swipe their card, and run the event.
But for the B2B SaaS side (wedding studios and event agencies), I absolutely use the dual-pricing to my advantage during sales calls. When I'm talking to an agency that shoots 40+ events a year, I'll actually point out the pay-per-event price first.
I’ll say something like: "If you do this one-off, it’s $X per event. But since you're doing high volume, the unlimited SaaS subscription brings your cost down to basically 20% of that."
Having the single-event price visible acts as an incredible anchor. It immediately validates the ROI of the subscription for power users, so I spend way less time defending the monthly price tag, and more time talking about the product itself.
That’s a useful distinction. It sounds like the two models are doing different jobs in the buying process.
Would be good to compare notes sometime — what’s the best email to reach you on?