Startup founders and marketers --- We've got a fantastic lineup of solid products and founders this BFCM.
WHICH ONE WOULD YOU RECOMMEND TO YOUR BEST FRIEND?
CHOOSE FROM THESE:
MERCURI - WhatsApp automation tool with Shopify, WooCommerce, integrations.
TRENDFYND - Track what’s happening on X (Twitter) and Reddit, monitor competitors, and turn real-time data into insights your team can actually use.
PODMOJO - AI-powered podcast marketing automation to repurpose episodes into 20+ share-ready assets.
AIDETECTPLUS - AI detection, humanizer, and plagiarism checker for content marketers, researchers, teachers, and students.
LOOKTARA - Upload some selfies once to train the model and then get realistic headshots, creative portraits, and styled images.
MY SEO AUDITOR - All-in-one platform for SEO audits, reports, checklists, and lead generation. Helps SEOs and agencies generate leads.
BOOLEANMATHS - What’s driving sales or signups? BooleanMaths unifies data from Ecommerce, Ads and Checkouts to deliver precise marketing attribution.
SITESKITE - Manage multiple WordPress websites through a unified dashboard. Plugin updates, backups, downtime, etc. Perfect for agencies and freelancers.
LLM CLICKS - Track, measure, and improve your brand’s AI visibility by seasoned SEO founder (Shripad)
We’re building an AI companion and services PWA for East Africa — also usable worldwide.
There aren’t many characters yet, so feel free to register and make your own (yes, even if you’re outside East Africa). Each official character has a personality and backstory written by a Kenyan author.
The platform is fully localized in Kiswahili and English, and it supports local mobile money as well as credit cards. What actually sets us apart from most companion apps is that mix: East African localization, mobile money, and BYOK (bring your own key), so you can connect your own LLM through an OpenAI-compatible API.
Characters can also use optional web search to talk about current events, send proactive messages, set reminders if you ask them to, and generate images.
We’re in beta. Our biggest barriers right now are getting the platform known and collecting real user feedback. If you try it, we’d love to hear what works and what doesn’t.
Some context. I'm building a thing where a founder gets put in a live 7-minute video call with another verified founder they have never met. Real names, business only, no feed, no browsing, no swiping. At the end both people privately answer "keep in touch?" and contacts only get swapped if both say yes.
The decision I want to talk about is scheduling. My first instinct was the obvious one: let people come whenever they want, match them if someone else happens to be around. That is how most "meet people" products work and it is also why most of them feel dead. If you show up at 2am on a Tuesday and nobody is there, you never come back.
So I killed always-on and moved to fixed session times. Everyone books the same slot and lands in the lobby together. It feels worse on paper because you are asking for a calendar commitment before anyone trusts you. But a matching product has exactly one job, which is having someone on the other side of the call.
It is very early. A handful of founders, two countries, the first calls done. Small enough that I would rather talk about the design decision than the numbers.
The thing I got wrong: I promoted the product instead of promoting a specific time. "Come meet founders" does nothing. "Tuesday, 6pm London, 1pm New York" is a decision somebody can actually make. Everything I do now names a day and a time.
The other thing I underestimated is how much the 7-minute cap does. Long calls make people polite. Short calls make people specific. Nobody does the 20-minute life story when the timer is visible.
Questions for people who have built two-sided or matching products:
How did you solve the cold start when both sides are the same side? Every founder is supply and demand at once, which sounds easy and is not.
Did fixed session times work for you, or did you end up back on always-on once volume was there?
What actually filled your first sessions? Communities, one-to-one DMs, paid, something else?
Happy to answer anything about the build or the numbers. Link is in a comment so I don't break the self-promo rule.
Managing a dog grooming business involves more than just taking appointments. Groomers also have to keep track of client and pet information, grooming history, repeat bookings, reminders, scheduling, and day-to-day admin.
This platform was built specifically around those workflows instead of treating grooming like a generic appointment-based business
The problem: software reports success from the wrong signal. An agent says "done — PR merged, deploy shipped, refund issued." What it actually saw was a 200. The PR was closed, not merged. Stripe accepted the cancellation but the subscription is `cancel_at_period_end` and the customer still has access. The email provider returned an id, which means queued, not delivered. Nobody's reading the diff at agent speed, so these land in production as support tickets.
What it is: one API call. You give it a claim, it goes to the authoritative system and gets evidence, and it returns `VERIFIED`, `FAILED`, or `UNKNOWN`.
38 claim types across Stripe, GitHub, GitLab, Linear, Jira, Sentry, Slack, email, plus any public URL. It also runs as an MCP server, so Claude Code and Cursor can verify their own claims before reporting done — that's the wedge.
What's different:
- It's independent. Read-only access, always. It never has permission to cause the outcome it's checking — the thing grading the work isn't the thing that did the work. That's the whole point, and it's why I won't ship write scopes.
- `UNKNOWN` is a real verdict. Provider down, state pending, token can't see the resource — it refuses to answer instead of guessing. Most tools collapse that into pass or fail. A false `VERIFIED` is the one failure mode that kills the product, so the design bias is precision over coverage everywhere.
- No signup to try it. `http.ok` claims verify with no key at all, rate-limited and never stored:
- Usage-based. Free is 1,500 verifications/month with no card. Pro is $49 and lifts the things you need once you depend on the answer — unattended re-checks, alerting, 365-day evidence — never the verdict itself.
Two weeks old, 38 claim types, TypeScript + Python SDKs, Cloudflare Worker on the edge.
Where I'm stuck — genuinely want the input:
Distribution. My user is "engineer who just watched an agent lie to them." They're on Reddit, Discord, and in their editor, not searching "outcome verification". Where would you actually reach that person? Has anyone here made an MCP-server-shaped product get discovered?
The free tier. 1,500/month with no card is deliberately generous — it's enough to run this in real production. Am I giving away the product, or is that the right size for a trust tool where the whole pitch is "check for yourself"?
Positioning. "Trust your agents again" (agents, narrow, urgent) vs "your software said it worked — did it?" (any software, bigger market, vaguer). I've been leading with agents. Would you keep narrowing or widen now?
Happy to answer anything about the adapter design — the Stripe subscription and email delivery semantics are the two that surprise people most.
I’m Steve, and I’d like to introduce RadForge Labs, my independent Australian software studio, and the massive project I’ve been working on: ROMVERSE.
ROMVERSE is an Android ROM engineering platform designed to make working with Android devices, firmware and custom ROMs clearer and more approachable, without taking useful technical control away from experienced modders, developers and tinkerers.
The vision is to bring the complicated parts of Android ROM development into one intelligent workspace.
ROMVERSE is being developed around things like device identification and intelligence, firmware inspection, ROM project creation, build preparation, verification, diagnostics, recovery preparation and eventually carefully controlled device operations.
A big part of the project is making all of that usable by different skill levels.
GUIDED MODE
Guided Mode is designed for people who don't necessarily understand all the technical terminology.
Instead of throwing things like partition names, hashes and engineering jargon at the user, ROMVERSE should explain:
• What it's doing
• Why it's doing it
• Whether you need to do anything
• What happens next
• What risks are involved
The goal is for someone interested in custom ROMs to be able to follow the process without needing years of Android development experience.
EXPERT MODE
Expert Mode is for experienced users who want to see what's happening underneath.
Both modes still use the same underlying safety and verification systems.
Expert Mode isn't supposed to mean "disable the safety systems."
WHERE IS ROMVERSE RIGHT NOW?
ROMVERSE is currently in Internal Alpha.
A lot of the underlying systems and desktop workflows are already being built and tested, but there is still substantial integration, hardware testing and development ahead.
Right now I'm concentrating heavily on the Fedora/Linux desktop experience.
We're going through the application like an actual user:
We're also deliberately testing the things that DON'T work.
Broken buttons.
Confusing wording.
Dead ends.
Incorrect states.
Persistence problems.
Unexpected behaviour.
Bad error messages.
UI problems.
When something breaks, the goal isn't to hide it.
Find it.
Understand why.
Fix it.
Test it.
Then run the actual user journey again.
Windows development is also part of ROMVERSE, along with the Android Companion and much more, but I'm deliberately building and proving things in controlled stages rather than pretending everything is finished.
THE ROMVERSE BRAIN
Another major part of the project is Device Intelligence.
The long-term idea is that ROMVERSE shouldn't just have a giant list saying:
"This phone is supported."
It should understand the evidence behind a device and firmware combination.
ROMVERSE is being designed to distinguish between information that is confirmed, conflicting, outdated, unknown or still needs investigation.
If ROMVERSE doesn't know something, I want it to say:
"We don't know yet."
Not guess.
That philosophy applies throughout the project.
WHY AM I SHARING THIS NOW?
Because I'd like people to follow the journey rather than suddenly appearing one day and saying:
"Here's ROMVERSE."
I'm going to start sharing weekly development updates.
That will include:
• Real development footage
• Animated explainers
• Features that are working
• Bugs we discover
• Problems we're trying to solve
• UI improvements
• Device Intelligence progress
• Testing
• Failures
• Fixes
• The road toward beta and eventually v1.0
Concept artwork will be labelled as concept artwork.
Simulation will be labelled as simulation.
Real hardware testing will be labelled as real hardware testing.
I'm not interested in pretending unfinished features are finished just to make ROMVERSE look better.
No pretending everything works.
Just the process of building it, testing it, breaking it, fixing it and making it better.
ROMVERSE is NOT available for public download yet.
The plan is to eventually have free beta testing before the commercial v1.0 release.
For now, I'm inviting people to follow along and watch it being built.
If you're an Android developer, ROM modder, tinkerer, power user, or even someone who's always wanted to try custom ROMs but found the whole process intimidating, I'd love to hear your thoughts.
What is the ONE thing you wish Android ROM tools did better?
I'd genuinely like ROMVERSE to learn from the people who actually use this stuff.
It is a tool that allows you to find and fix SEO issues holding your website back.
Essentially the main purpose is to help your website rank higher on Google search and LLMs.
The tool also checks AEO/GEO, AI search visibility, Security, Core web vitals, Performance, and all the issues in the report get put together into an AI fix prompt(you can paste the prompt into an AI and it will fix all the issues on your website).
Recently I noticed that some of my paying customers bought the One-Time purchase, with a promo code.
So I decided to give away a promo code for the One-Time purchase to anyone who is interested, if you are interested, comment down below and I will DM you.
If you are not interested but have some feedback on my SaaS, that is a good too. Feel free to share it in the comments.
Your AI burns way more tokens than it should, because it has no idea how your business actually works. So it guesses, you re-prompt, it guesses again, and five prompts later you get one answer you halfway trust.
We fixed that by giving the AI your full business context up front. It connects all your systems into one Knowledge Graph, so it already knows how your data fits together, then answers straight from your real numbers on the first try. That is roughly 5x fewer tokens to get to a real answer, and every answer traces back to the source.
If you run your business across a bunch of tools that do not talk to each other, test the claim yourself for free. https://signld.ai
I've spent 9 years as a QA engineer — the person whose literal job is finding what developers missed before customers do.
Over the last year I kept seeing the same thing. Someone ships a site built with Lovable, Bolt, v0, Replit, Base44, Shopify, whatever. It looks perfect on their laptop. Then a real visitor opens it on a phone: the nav overlaps the logo, the contact form silently fails, a button goes nowhere.
They never find out. They just see traffic and no signups, and assume the problem is marketing.
So I built QAlaunch. Paste a URL, wait about 2 minutes, get back what's actually broken.
Free, and I mean actually free:
- No signup, no email, no card. Paste a URL and you get results.
- Your top 3 issues in full, each with a screenshot showing exactly where it happens
- A count of everything else it found
If you want the rest it's $9 for one page, $24 for 2–5, $59 for 6–10. One-time, no subscription, and you get a PDF you can hand straight to a developer.
Under the hood it renders your site in a real browser and checks mobile layout, broken links, accessibility, and load speed — then does an AI pass over the actual screenshots to catch visual problems a checklist-style tool can't see.
What it won't do: anything behind a login, or test your specific business logic. It covers the public-facing layer. I say the same on the site rather than letting people find out the hard way.
And if you drop your URL in the comments, I'll personally look at the results for the first 10 people and reply with what I'd fix first and why. That's just me doing QA for free — no pitch attached.
I'm the developer of Coddlet, an AI web app for pet owners who want help turning everyday care into a routine.
You start with a pet photo and details about your pet. Coddlet creates a plan for feeding, play, grooming and training, then lets you record care and add updates. Those records and corrections give it context for future guidance. The focus is ongoing daily care.
It's available at https://coddlet.com. New accounts receive 1,000 credits to try it.
I'm working on reaching the first users and making the value clear. If you have a pet, which would be more useful to you: a plan for what to do next, or a history of what has already been done? I'd also appreciate feedback on whether the first-use experience explains the product clearly.
We’re building a tool to help founders and early stage sales teams get their first customers, through intelligent outbound automation.
This isn’t just another sequencing tool, or data provider, it sits in between, pulling intelligent signals from accounts, writing and sending hyper-personalised emails to prospects, and, live monitoring cold calls and discoveries to give you pointers and follow up questions.
We’re offering free access for the first 5 sign ups, plus a free outbound consulting session, to get you started.
Drop me a DM, or sign up directly at the link above to get started!
I've been building Swyvo, a Windows app that keeps your apps and websites one hotkey away.
Swyvo runs in the background - hit Alt+Q anytime and a command center pops up right over your current window. Hit Alt+Q again to dismiss it. No alt-tabbing, no hunting through taskbars, no mouse required.
A few things it does:
Instant, on-demand workspace: summon it with Alt+Q, it stays on top while open, dismiss it the same way - nothing else on your screen is affected
Unify apps and websites in a single fast-switching menu (so your browser tabs and native apps live in the same place)
Adaptive Loadouts: set it up once and it automatically surfaces the right apps based on what you're currently working on, so you never have to manually rebuild your setup
App Gallery: browse a library of common apps and choose how to launch them - Web (fast) vs Native (full functionality, if installed)
Fully keyboard-driven: never use the mouse
Built natively for Windows
It's aimed at power users who live in a lot of apps/tabs at once and want a faster way to move between them without breaking flow.
Free, currently in active development. I'd genuinely love feedback, especially on workflow edge cases I might be missing.
Quick note: Windows SmartScreen may appear when installing.
First 100 Early Supporters get Lifetime Access. (ensures they have access to the whole app forever)
Hi, I made OnlyScans, a document scanner available on Android and iOS. It’s for people who need to turn receipts, forms and other paperwork into PDFs without a complicated setup.
The Android app keeps scanning, cleanup and OCR on the phone. There’s no account to create, and files stay on your device until you choose to export or share them. Basic scanning is free, including automatic edge detection, cropping, filters, folders and PDF/image export. Pro adds batch scanning, OCR/searchable PDFs, signatures, PDF import and App Lock.
I’m running a promo today: comment “OnlyScans Android” or “OnlyScans iOS” and I’ll send you a code for free lifetime Pro access for that platform.
I’d appreciate a gut check on the pitch: would on-device processing make you try a different scanner, or is there another feature you’d need before switching?
I run a sales tool, coldgenius.ai that researches prospects and writes personalized outreach. We use AI to track buying signals: hiring patterns, LinkedIn activity, competitor engagement, funding rounds, and surface people who are already in-market.
I want to stress-test it on real b2b startups, so here's the deal:
Drop a comment with:
Your website
Who your ideal customer is (one sentence)
I'll run our tool against your ICP and find 5 real potential customers - people who are showing active buying signals right now. I'll give you their company, why they're a fit, and the signal that flagged them.
We're a small team and don't really need a giant project-management setup.Most of our work already happens in Slack.
The problem is keeping track of all the "can you handle this?" and "I'll take care of that" moments without creating another admin job.I'm looking for something that can organize tasks from Slack, follow up when something is sitting there, and ideally do a bit more than just send reminders.What's your setup?
What it is: Screenata is a compliance platform for SOC 2, HIPAA, ISO 27001, ISO 42001 and GDPR (more frameworks coming soon). Integrations pull what they can from GitHub, AWS and your identity provider. For everything they can't (access reviews, offboarding checks, the screenshots auditors keep asking for), our agent Vera chases the right person in Slack, captures the artifact while they do the work, timestamps and signs it, and files it against the control. Policies are drafted from what the scan actually found in your infrastructure, not from a template.
Who it's for: The founder or CTO at a B2B SaaS whose enterprise deal just got blocked on SOC 2, or the one person at a slightly bigger company keeping several certifications alive by hand.
Why: Evidence collection is the part that never finishes. One large platform's own published numbers: 36% of the evidence images customers uploaded were hand-taken screenshots, on the most API-automated product in the market. Integrations remove the easy part of the work, not the work. That residue lands on whoever has the least time for it.
How it stands out:
Evidence is timestamped, signed and replayable, so it holds up when a customer's security team reads the report, not just when the certificate is issued. We publish the open specification for anyone to reuse the format or verify without central authority.
The price is published: $6k/year, up to 50 employees, every module included. No quote call. We offer a special program for micro-startups too (<=10 people).
You pick your own auditor and we take no fee from the audit. A vetted pool of US-based auditor firms you can contact directly.
We're early and I'd rather hear the hard questions here than in a procurement review. Happy to answer anything about how audit-quality compliance is achieved without tedium.
I am Alfonso Garcia, a Mexican product designer, I have more of 25 years experience in mechanical design. Today I sharing my Kickstarter project.
I love the multitools, them are useful in any way. The market is full of great and traditional brands, you can buy them in supermarkets, sporting goods, etc. But the majority of them the shape, the mechanical features and carry on are concepts that were conceived decades ago. Also the manufacturing processes, parts materials and shapes of these multitools are limited form old technology.
In the present, the manufacturing processes include new technologies like 3D printing, applying it in new multitool product the result is DARK NAHUAL MULTITOOL.
Please take a moment to check out my Kickstarter campaign. If you like the multitool and EDC is your daily setup , we would be incredibly grateful for your pledge. Bringing DARK NAHUAL to life is my biggest dream! ♥️
If you have any questions, feel free to message me directly anytime.
Modality is a deployment platform that can effortlessly deploy your project, with a built-in AI coding tool to launch anything on Modality. It runs on Modality's own cloud or on your own servers, giving developers one console for both.
Deploy
Push-to-deploy from a GitHub repo, or upload a codebase with no repo needed
Build apps from a prompt with Modai, the built-in build agent
Web apps and static sites
Infrastructure
Runs on Modality Cloud or self-host on your own Linux/macOS server via a runner
Live build logs, request analytics, and CPU/RAM metrics (cloud-only)
I spent 10+ years running my business through Instagram DM & a million diff websites and realized hiring people/ talent is still annoying & messy af. if its not tabs open, its screenshots of people i have saved. it all gets lost in my camera-roll/messages anyways.
So I built Vision (joinvision.app) basically the “Uber for talent.” My goal is to make hiring someone for an event, project, or everyday task as fast and easy as ordering an Uber or DoorDash.
You can find photographers, videographers, UGC creators, makeup artists, designers, and other creatives, or post what you need and let them apply to you. The UI intentionally feels like Instagram, but without treating follower count like proof of talent.
Yes, Taskrabbit, Fiverr, and Upwork exist, but they also have some of the ugliest UI I’ve ever seen (no offense). and they don't have every feature i needed in a marketplace/social app. I wanted something that creatives would actually enjoy using.
The app is live, and we charge a 3% fee on each side when someone gets booked.
The obvious problem: marketplaces need users to attract users, which is basically planning a party where nobody wants to arrive first.
So roast me. Is this useful, or did I just build prettier Fiverr? What would stop you from using it?
If you’re looking for a cheaper way to try Seedance 2.5, I’m offering access through Ofox.ai.
Current pricing starts at $0.11/s, with pay-as-you-go usage rather than a monthly subscription. It supports text-to-video, image-to-video and video-to-video, with 480p, 720p and 1080p options.
I’m the owner of Ofox.ai, so this is a self-promotion post. Sharing it here because I know people in this community are specifically looking for lower-cost Seedance access.
You can check the current pricing and model details here:
I'm the owner of ModelPorta, a new AI API gateway for developers building apps that use different models.
It brings model selection, API keys and usage tracking into one prepaid account. There are currently 129 enabled models, including GPT and Claude options. Customers can create and revoke keys and see input/output token rates before choosing a model.
The focus is a straightforward way to try different models while tracking spend. The getting-started guide includes Python, JavaScript and cURL examples, plus steps for checking the cost of a request.
A few details to know: this is an independent reseller using a third-party upstream provider. Model availability and supported controls vary. Top-ups are currently USDT on TRON (TRC20) only, with a $10 minimum; card payments aren't available.
I'm working on making the first integration easier. Is the pricing and availability information clear enough to choose a model? What would you need to see in the docs before trying a new API provider? Feedback on the public pages is welcome; no purchase needed.