6 products are running in production. They have domains, landing pages, and working payment integrations. Hit the checkout button and you'll actually get charged.
But revenue is $0.
To be precise, not a single user has ever paid. The services are live, infrastructure costs go out every month, but nothing comes in.
This is not an excuse. It's an analysis. What I did, what I didn't do across 6 products, why I'm sitting at $0 -- and the decision that came out of it.
6 Products, Each With Its Own Story
1. vibecheck -- Multi-device Claude Code Access
A service that lets you use Claude Code across multiple devices.
It started from the idea of breaking free from the constraint of Claude Code only running in a local terminal. Sometimes you start a task on your laptop and want to pick it up on your desktop, or check on it from your tablet. That's the problem I set out to solve.
Current status: Posted on Reddit a month ago. One person signed up yesterday.
- Signups: 1
- Paid conversions: 0
- Revenue: $0
Zero response for a month, then suddenly one signup yesterday. That's the reality.
2. b4uship.com -- Pre-launch Code/URL Scanner
A tool that scans your code and URLs before you launch.
Simple concept: "One last check before you ship." It catches security vulnerabilities, broken links, basic SEO issues -- things you want to catch right before launch. The goal was to be the final checklist a developer runs before putting a side project out into the world.
Current status: No marketing yet. Mentioned it during a mentoring session -- "give this a try" -- and one person signed up.
- Signups: 1 (from mentoring referral)
- Paid conversions: 0
- Revenue: $0
3. build.drillcheck -- Market Demand Analysis (Reddit Data)
A tool that analyzes market demand using Reddit data.
It shows what people are frustrated about on Reddit and what solutions they're looking for. The idea was to answer "Is this idea any good?" with data instead of gut feeling.
Current status: Not a finished product yet. No marketing either.
- Signups: 0
- Revenue: $0
The irony: I built a tool for validating market demand without validating the market demand for the tool itself.
4. career.drillcheck -- Freelancer Skill Trend Data
A service that shows which skills are trending in the freelancer market.
It tracks which technologies are in demand on platforms like Upwork and Fiverr, and how rates are changing. The goal was to give freelancers data to help them decide what to learn next.
Current status: No signups.
- Signups: 0
- Revenue: $0
5. drillcheck.app -- Interview Prep SaaS
A SaaS for technical interview preparation.
It helps you systematically prepare for coding interviews and system design interviews.
Current status: No signups.
- Signups: 0
- Revenue: $0
6. littlestory.me -- Children's Photo Album
A niche service that turns your kid's photos into photo albums.
This one is different from the other five. It's not a developer tool or B2B SaaS -- it's a consumer product. Parents upload photos of their kids, and it creates a beautiful photo book.
Current status: One person signed up but never actually used it.
- Signups: 1 (inactive)
- Orders: 0
- Revenue: $0
The Scoreboard
- vibecheck: 1 signup, $0
- b4uship.com: 1 signup, $0
- build.drillcheck: 0 signups, $0
- career.drillcheck: 0 signups, $0
- drillcheck.app: 0 signups, $0
- littlestory.me: 1 signup (inactive), $0
Total: 3 signups, $0 revenue. That's the reality.
Why $0
All 6 products at $0 is not a coincidence. There's a pattern. It means I kept making the same mistakes.
Here's the honest breakdown.
I built first
This is the biggest problem. Every single one of these 6 products started with "wouldn't it be nice to have this." Not "would someone pay for this?" but "can I build this?" was the starting point.
I could build it. I did build it. But I couldn't find anyone to use it.
This is the Build First trap. It's the easiest trap for engineers to fall into. If it's technically feasible, it feels worth doing. And once you finish building it, you assume people will come. They don't.
I didn't do marketing
After building a product, what I did next was build the next product. I started building the second one before finding users for the first. I was already planning the third before the second was even done.
vibecheck got posted to Reddit once. That's it. The rest have had zero activity that could be called marketing. b4uship was mentioned once during a mentoring session. That's the extent of it.
Building is fun. Selling is hard. So I just kept building.
I didn't experiment with pricing
All 6 products have pricing pages. All have payment integrations. But I never validated whether any of those prices were right.
Was the plan to let people use it free, collect feedback, then convert to paid? Or was it to charge from day one? That wasn't even consistent across products. Translation: there was no pricing strategy.
The problem of spreading thin
If I had focused on 1 product, things might have been different. Time, energy, and attention split across 6 was never enough for any of them.
Each one took about a week. With vibe coding, that's enough to get to production. Add it up and it's roughly 6 weeks. 6 products in 6 weeks. I was proud of the speed.
If I had spent those 6 weeks on one thing -- 4 weeks building, 2 weeks marketing -- the number might not have been 3 signups.
So what did I learn
What $0 in revenue taught me is clear:
- Sell before you build. Put up a landing page, collect pre-signups, and find out if anyone cares first.
- Focus on one thing. Running 6 products at $0 is worse than running 1 product at $100.
- Marketing is not optional. There need to be days where you don't write a single line of code. Spend that time writing, talking to people, getting the word out.
- Kill fast. Some of these 6 need to be shut down. It's emotionally hard, but necessary.
The Pivot: From Solo Builder to Build Partner
Here's the thing. While I was building 6 products nobody used, something else was happening.
I was mentoring junior developers. Reviewing code written by non-developers using vibe coding tools. Helping people who had ideas but couldn't execute them.
And I realized: I'm pretty good at this part.
Not the "having ideas" part. Not the "marketing" part. The building part. Taking someone's concept and turning it into a working product in days, not months. Setting up payments, databases, auth, deployment -- the infrastructure that first-time builders struggle with.
The problem with my 6 products wasn't the building. It was that I was building for myself, in isolation, with zero market validation. But what if I wasn't the one with the idea?
What if someone else brought the idea, and I brought the execution?
That's the pivot.
ContentsTailor is now a micro venture studio.
Not an agency. Not freelancing. A build partner.
Here's how it works:
- You bring the idea. A side project, a SaaS concept, a tool you wish existed.
- We validate it together. Using real data, not gut feeling. (That's what build.drillcheck was made for.)
- I build the MVP. Fast. Usually within 72 hours. Payments, auth, database, deployment -- all handled.
- We launch together. Including a security scan with b4uship before going live.
- We grow it together. Marketing, optimization, iteration. Until the product can stand on its own.
- You graduate. When the product runs independently, you take full ownership and walk away with a working business.
Every step gets documented on this blog. Build logs, launch reports, growth experiments, failures. All public.
Why this is different from an agency
Agencies build what you ask for, hand it off, and invoice you. If it doesn't work, that's your problem.
This is a partnership. I have skin in the game:
- Build fee + revenue share. I'm incentivized to build something that actually makes money, not just something that ships.
- Support until graduation. I don't disappear after deployment. The partnership continues until the product can run without me.
- Full transparency. The entire process is published as content. You can read other project stories before you even reach out.
The 6 products become the portfolio
Those 6 products at $0? They're not failures anymore. They're case studies.
- b4uship is a tool I use in every project launch. I wrote about how I built it in 48 hours.
- build.drillcheck is how I validate ideas before building.
- vibecheck is how I develop from any device.
- The blog itself is the content engine that drives the entire flywheel.
Each project I take on uses these tools. Each project becomes a blog series. Each blog series attracts more people with ideas. The flywheel spins.
What's Next
Here's the concrete plan:
1. Document the build process
Every project gets a series on this blog:
- Build -- how the MVP was created
- Launch -- what happened when it went live
- Grow -- getting users, getting revenue
- Autopsy -- if it fails, why it failed
2. Monthly build logs
On the first of every month, I publish a build log with real numbers:
- Revenue (studio + SaaS)
- Active projects and their status
- What worked, what didn't
- Plans for next month
The first one will be mostly zeros. I'm publishing it anyway.
3. First external project
I'm actively looking for the first project partner. Someone with an idea, willingness to commit, and a problem worth solving. If that's you, reach out.
The first project will be documented in full detail -- from the initial conversation to MVP to launch to growth. Every decision, every mistake, every win. Public.
Wrapping Up
6 products. $0 revenue. 3 signups. Those numbers haven't changed.
But the strategy has.
I'm done building alone in the dark. I'm done being the person with the idea AND the builder AND the marketer AND the support team for 6 different things.
Instead, I'm going to do what I'm actually good at: build products fast, ship them reliably, and document the entire process. For people who have the ideas and the hustle but need a technical partner.
This blog is the record of that pivot. The build logs, the project series, the failures and the wins -- all of it, transparent and public.
If you have an idea and need a build partner, apply here.
If you just want to watch the journey, bookmark this blog. The numbers will change. And you'll see exactly how.
ContentsTailor is a micro venture studio. We build products with people who have ideas, grow them together, and document the entire process. Learn more or apply to partner.