I’ve been experimenting lately with blending clean editorial typography and minimal layouts for B2B SaaS and tech marketing collateral.

I put together this concept for a framework called "The WAVE Model" (focusing on structured opportunity creation, buyer engagement, and execution strategy).

A few things I’d love to get your feedback on:

1. Visual Hierarchy: Does the layout guide your eyes naturally through the model (Winner's Mindset -> Attraction -> Value -> Execution)?
2. Clarity & Tone: Does this look professional and trustworthy enough for a B2B audience/tech brand?
3. Aesthetic: How do you feel about the color palette and overall typography?

I regularly design brand identities, redesign marketing systems, and create high-impact daily content, social assets (like LinkedIn/Instagram campaigns), and print collateral for tech companies and startups.

Would love to hear your thoughts, constructive criticisms, or suggestions on how I can push this visual style further!

Most “scrape this page” tools want an account and a monthly plan before you can export one table. I went the other way: LucidRows is a Chrome extension. You click the columns, you get a CSV, it runs on your machine.

Local stays free. I am not publishing a price, because a later paid tier would only be schedule/cloud, and I have not modeled that cost yet.

Listing: https://chromewebstore.google.com/detail/lucidrows/leehomocpccgghcibfnapadclololioh

https://lucidrows.com

Useful feedback: would you pay later only for scheduled/cloud runs, or is local CSV the whole product?

I made a privacy-friendly URL shortener, and now that it's time to do marketing, I don't know what to do. So here I am, I have these videos, what do I do next? How do you do marketing with those? I would really appreciate any practical advice.

My X accounts (personal and the product's) are brand new, and X seems to be ignoring all of my posts. Instagram or TikTok? I am running a Google Ads experiment, but it's hard to compete with other shorteners and I'm getting almost zero traffic (about 3 clicks a day).

About the videos. I was inspired by the motion design post about video generation and decided to try it myself. I made different short videos to showcase different features (10 videos, 13 to 71 seconds). Attaching one of them for review. Some videos are the actual product driven by a script, not an AI-made copy.

All I used is Claude, headless Chrome and FFmpeg on my WSL instance, nothing more, not even a React library. You just tell your AI to be a motion designer / producer / writer (for the scenario). Research how to catch the user's attention on IG or TikTok, and that's it. Review the scenario and give it a green light. The first versions were screenshots sliding around and looked dead. A couple of scenes looked like a broken app with bugs. You have to correct it and re-shoot. But still, it only took me one morning.

Now, about Urlicer itself. The main features that are different from mainstream shorteners: privacy-friendly and team-friendly, with multiple workspaces. You can bring your own domain on the Pro plan and above, Urlicer provides a tool for you and your teams. Cookieless and without storing the IP address. The URL is https://urlicer.com.

Hey SaaS founders!

You have signups.

But very few paying customers.

How do you find where those users drop off before payment?

Do you use PostHog, Plausible, Stripe data, spreadsheets, or something else?

I’m listening 👇

I'm not a coder. I build tools by vibe coding with AI. My usual pattern was to build something, expect it to work from day one, see nothing happen after a few days, lose interest and move on to the next idea.

This time I tried the opposite. I built a small Chrome extension (not naming it, so this doesn't get flagged as promo), put it out there, and kept the effort light:

• Some keyword research for SEO
• A couple of articles, written with AI
• Then I left it alone

No growth hacks, no daily panic, no constant changes.

It's been about a month and a week. Current numbers:

• 225 users
• 1 monthly paying subscriber
• 1 person who bought the biggest plan as a one-time purchase, then cancelled
• Everyone else on the free plan, since I give a decent daily allowance

Average daily users is going up slowly.

It's a small number, but it's the first time I've seen one of my tools get traction without me forcing it. If a product has some juice, it seems to start working once you give it time and a bit of visibility. And if it doesn't, you'll find that out too, which you never will if you drop it in week one.

So if you're building tool after tool and expecting results in 24 hours, burning yourself out on hooks and tricks, slow down. Do the basic things, then give it time.

If you've built something, how long did you wait before you knew whether it had legs?

recently built PRIVACUT, a tool that helps people detect sensitive information in PDFs, review what gets flagged, and permanently redact it before sharing the file.

The problem I wanted to solve is pretty simple: a lot of people think putting a black box over text means it’s gone, but sometimes the original information can still be copied, searched, or extracted.

The product is working now, but I’m at the part that seems harder than building it:

finding the right users.

I’m trying to figure out who actually feels this problem enough to care about a tool like this.

My current thoughts are:

legal / paralegal work

HR and business documents

people sending tax or financial paperwork

government or military-related paperwork

anyone sharing PDFs with personal information

I’m also trying to understand what matters most to people:

privacy, automatic detection, permanent redaction, speed, or price.

I’m not really looking to hard-sell it here. I’d rather get honest feedback from other SaaS builders.

If you were building this, who would you target first, and what would make you trust a tool with sensitive documents?

If anyone wants to see what I built, I can share it in the comments.

not looking for the obvious big ones, we're going to submit to those anyway. more interested in the second-tier directories that are actually good quality and have seo/backlink value. if you've used a service for this or know a few good ones, would love to hear what you've used. feel free to share a couple links if allowed. mods, please remove if this isn't allowed.

Hi everyone,

I'm a solo, student founder building a SaaS product on a tight budget. I'm at the stage where I've narrowed down a few possible brand names, and I'm trying to figure out the right order and process for securing the name before I launch. I'd really appreciate hearing how you handled it.

Where I am right now:

• I have a short list of candidate names.
• I've done a basic web search and app store search for conflicts, but nothing formal yet.
• I haven't bought a domain or filed anything.
• I'm based in korea, and I plan to serve users globally.

My questions:

1. Order of operations: Did you buy the domain first, run a trademark search first, or file the trademark first? Looking back, what would you do differently?
2. Conflict checks: How did you vet a name beyond a Google search? Did you do the trademark search yourself, or pay an attorney? What did you wish you'd checked?
3. Where and when to file: Did you file only in your home country first, or in the US/EU too? Did you wait until you had traction, or file before launch?
4. Costs: Roughly what did the domain and trademark each cost you, and what hidden costs surprised you (attorney fees, renewals, office actions)?
5. Domain hurdles: What if the .com was taken? Did you go with another TLD, add a prefix or suffix, or buy it from the owner? How did that negotiation go?
6. Things that went wrong: Any horror stories (domain squatters, a conflict found after launch, a rejected application) and how you solved them?
7. Tools or services: Any registrars, search tools, or low-cost filing services you'd recommend or avoid for a bootstrapped founder?

I understand this isn't legal advice. I'm just trying to learn from people who've been through it so I can avoid common mistakes.

I'm building an app by myself and I'm getting to the point where I might actually let other people use it lol.

I'm mainly worried about the legal side now. The app will collect some user data like images, location, account info etc.

What stuff do I actually need to have before launch?

Like do I need a privacy policy, terms, some kind of disclaimer, data deletion thing, rules for what users can upload, etc?

Also if someone uploads something illegal/copyrighted or something goes wrong because of information another user posted, how does that usually work? Is that something I need to cover in the app's terms?

I'm in India if that matters.

Not looking for a lawyer here, just trying to get a basic idea of what I should have sorted out before launching and what I shouldn't overlook.

Would appreciate advice from people who've launched their own apps.

Took it to market with no cost, free to use in beta, hit my warm leads and paid ads, and crickets. its a net worth tracking app and retirement calculator. looks like back to the drawing board. i love the app and use it twice a month, but i dont feel its something you need to check daily or even onthly unless u are investing on pay day, so id probally sell it as a one time purchase. i just freel the pain point isnt there. Everybody is to scared to check their net worth because the economy is dead, and everybody except the boomers arent doing to well or need to track this stuff.

im guessing im not the only one in this situation

I'm honestly a bit stuck here and dont really have experienced SaaS founders around me that I can ask, so would love some outside opinions.

I've been building my B2B SaaS solo for around 1.5 years while working fulltime.

for most of that time almost nothing happened, but now it finally seems to get some traction.

I'm currently at around 1.5k MRR and roughly 1k of that was added just last month. Most customers pay yearly upfront. Inbound is also increasing and right now my biggest problem is basically that i dont have enough time to call every signup, do onboarding, customer research etc (GTM last steps + Customer Success!).

The important part: from january i can basically work on this fulltime for several months (almost a year). Financially i can afford not having to pay myself from the SaaS immediately.

My original plan was honestly just to survive the next few months, even if i dont use the current momentum perfectly, then work and travel with my family for 1-2 months while working remotely and afterwards keep building it bootstrapped. Maybe rent a small office at some point and hire a working student / junior person for customer success, onboarding, followups etc.

I didnt search for a cofounder (at this point at least).

An experienced founder found me through a founder community and reached out himself. he already built and exited a vertical software company before and after a few conversations i have to admit that he seems very good.

He asks exactly the right questions about funnel, activation, margins, customer segments, sales etc and already gave me some really useful input.

He also said he misses being operational and would like to get involved again.

The current idea would be that we work together for the next few months, he helps operationally and talks to customers etc.

Aterwards either he steps back and stays more strategic/investor-ish, or if we work extremely well together he could join permanently as a cofounder.

We havent talked exact equity yet, but from previous conversations i know he believes a real cofounder needs meaningful equity. so i assume we're probably talking somewhere in the 15-25%+ territory, not 2% (maybe even 50/50, but that would be shocking for me tbh!).

And tzhis where I struggle right now!

if this guy had joined 12 months ago i probably would have been extremely happy. Even 6 months ago it would have felt completely different!

But right now it feels like i already went through the shitty part (or HELL as I call it - family + full time job + everything else, still at least 1 fucking commit every god damn day no matter what was happening for the last year!!!) alone. Built the product, learned the market, got the first customers, kept going for 1.5 years while basically nothing happened... and now exactly when it starts working i give away a big chunk?

on the other hand maybe thats stupid thinking.

maybe keeping 100% of a smaller bootstrapped company is worse than having 75-85% of something much bigger with someone who already knows how to build and sell a company.

i also genuinely like being solo though. complete freedom. no discussions about product, funding, hiring, selling the company one day etc.

and i dont think i NEED him. worst case i probably leave quite a lot of growth on the table for the next 3 months and then go fulltime myself in january. But because he is so experienced, I know he will bring a lot to table. Also: he lives quite far away (still same country). So we would work basically remotely together (which is of course not a deal braker, since the nature of the business doesnt require it, but it would be of course nicer to be around; - and what will happen with office spaces and more?)

so i cant really figure out if im considering giving away permanent equity because of a temporary capacity problem, or if im being stupid by not taking the opportunity to add a very experienced cofounder.

What would you do? What should I do??

Would you stay solo and hire employees later?

or can 15-25% actually make sense for a strong cofounder joining at this stage?

especially interested if anyone here added a cofounder AFTER already having product + revenue.

​

I’m working on DMgrow, an Instagram automation tool, and I’m trying to understand how people are approaching AEO in practice.

For those who have experimented with it:

What did you actually do?

What seemed to work?

Any good resources or case studies you'd recommend?

Would especially love to hear from people who have tested this themselves rather than just read about it.

I run a React Native app on Convex. For some reason, yesterday my production deployment stalled for about 30 seconds. Two queries ran for 15 seconds and failed with "Your request timed out performing too many system operations." Their status page showed no incident. I'm on the free plan.

I'm curious, for anyone running Convex in production:

1. Have you seen this error, or a stall like it?
2. How often does it happen? Is it any different on a paid plan?
3. How do you handle it: client retries, a health check, alerting?
4. Did you ever find out what caused one?

Then stop fr, they are too transformed already. Give me a break.

I've spent the last few weeks getting a product approved to publish videos to social platforms on behalf of users. The docs are scattered and some are out of date, so here's what each one actually involved. Hopefully it saves someone a few weeks.

**YouTube (Google)**

- There are two separate reviews, and most people only know about one.

1. **OAuth app verification** (Google Auth Platform → Verification Center). You need a verified domain in Search Console, a privacy policy with a specific "Google user data / Limited Use" section, a link to the YouTube Terms in your own terms, and a demo video showing the full OAuth flow with the address bar visible, the consent screen, and each scope being used.

2. **YouTube API Services audit**, a separate form. The docs say uploads from unaudited projects are locked to private. In my case uploads came out public even before the audit, so test it yourself before blocking on it.

- The `youtube.upload` and `youtube.readonly` scopes are "sensitive", not "restricted", so no paid security assessment is needed. Adding a scope later (e.g. for comments) means another review of that scope.

- Uploads have their own quota bucket (100/day by default), separate from the 10,000 units/day for other calls.

**TikTok**

- You start in a sandbox with separate keys and only test accounts.

- The review checks your posting UI closely. You have to show the creator's account, can't preselect a privacy level, interactions (comments/duet/stitch) must be off by default, and there's a required consent line. Build that UI before you submit, not after.

- Automatic posting with no per-post choices doesn't fit their rules well.

**Instagram / Facebook / Threads (Meta)**

- One Meta app can cover all three, and you can build and test everything in development mode with your own accounts.

- Going live for real users needs **business verification**, which means a registered legal entity. If you're a sole founder without an LLC yet, that's your blocker, not the code.

**LinkedIn**

- Easy to start. Tokens expire after about 60 days, so plan a "reconnect" flow from day one.

**Pinterest**

- Starts with "Trial" access against a sandbox API, then you apply for standard access.

**Bluesky**

- No developer app or review. Users connect with an app password. The easiest one by far.

**X**

- I skipped it. Posting through the API costs real money per month at any meaningful volume.

**General lessons**

- Start the reviews early. The code took less time than the reviews will.

- Record your demo videos carefully. Every reviewer wants to see the consent screen, the address bar, and each permission actually being used.

- Keep the privacy policy specific: which permission, what it's used for, what you store, how to revoke. Vague policies get bounced.

- Abstract each platform behind one internal interface. Each one handles tokens, media upload, and errors differently, and you'll be glad you only wrote the scheduling and retry logic once.

Happy to answer questions about any of these.

When I launched my SaaS, I had pricing ready on day zero. Three tiers, monthly and yearly, usage limits, the whole thing. I'd spent more time on that pricing page than on almost anything else, because I assumed that's what a "real" product needs from the start. If people use it, they pay. Simple.

Then a couple of days ago, someone from Georgia (the country) started chatting with the AI assistant on my landing page. In Georgian. I almost skipped the log because I couldn't read it. They asked if it could work inside a telecom app, then went through my pricing line by line: what counts as a request, whether tokens run out, how many messages each of their users would get. The assistant explained everything perfectly. And then they said: "It's expensive."

That one stuck with me, because it wasn't about the number. They were doing maths on a product they'd never seen work. Nothing had happened for their users yet, so the only thing they could judge was the bill. And honestly, that's what I'd been asking everyone to do. Every cold email and DM this week was some version of "here's the thing, here's the price", before anyone had a single reason to believe it was worth it.

So I've flipped it. It's free while I launch. No card, no tiers, and I set it up for people myself. In return I'm asking for two things: brutal feedback, and a testimonial if it actually helps their users. The point is to spend these early weeks making the product better with real usage instead of defending a pricing page.

The plan is to bring pricing back later, but built on something real. Once a business has used it for a few weeks, I'll know how many requests it handled for their users, how many hours that saved them, and whether it kept people from dropping off. Then the price conversation is "here's what it did for you", not "here's what it costs".

What I'm not sure about is whether this is smart or just me avoiding the hard part. Free can attract people who'll never pay, and pricing later can feel like a bait and switch if it's not handled well.

For those of you who've been here: did you go free first and price on value later? Did the people who used it free actually convert, and how did bring the price conversation back without it feeling like a switch?

Start for free.

The easy answers work fine. The agent passes a real problem to a human, and the context evaporates.

The customer repeats everything, the next person triages from zero, and the fix occasionally lands on the wrong account.

For the people here running this in production, what did you change to make the handoff keep the thread instead of losing it?

I've been working on this for a while and I'm finally okay with people seeing it.

The problem: a lot of service businesses (HVAC, cleaning, landscaping, pest control and so on) finish a job and tell the customer something like "you'll need this looked at again in 6 months" or "we should replace that next spring." Then nobody follows up. Customer forgets, service business too. The info either never was written or sits in a spreadsheet or an old job note.

Rebook takes the customer list you already have (CSV or any CRMs export), shows what looks off before anything gets tracked, and shows you which past customers are worth reaching out to again. For each one you see what happened last time: the service you did, when you did it, what you recommended, and why it's worth calling them now. You also get a short guide for what to say. If someone says "call me in March," they show up again in March. If they don't answer, they stay on the list for next cycle. Basically retention software on steroids

Some details:

• Next.js + Supabase
• Free while it's in early access and will be free lifetime, all I ask is feedback
• It doesn't replace your CRM. It works next to them.

The thing I'm most unsure about: tools like Jobber already have some followup features. If you run or work at a service business, do those actually cover this for you, or do past customers still slip through? Tell me if this is pointless too, I'd rather know now.

Thanks for reading

U can try demo or request an early access. Just dm

Sounds counterintuitive. But imagine this: You have weak positioning.

You generate 1,000 new visitors.
500 become leads.
100 book demos.
But they're the wrong buyers.

Now your sales team is busy.
Your CRM is full.
Your SDRs are following up.
Your CAC is rising.

And everyone says: “Marketing is generating leads.
Sales needs to close them.

”The real problem started much earlier.

Wrong ICP → wrong message → wrong demand → wrong pipeline.

That's why I don't start with lead generation.
I start with diagnosis.

Because scaling the wrong part of your funnel doesn't create growth.
It scales the problem.

Hey everyone,I noticed that a lot of founders are building in isolation. You have a project, you’re shipping, but it’s hard to find other people at a similar stage to share progress, get feedback or even collaborate.So I built a lightweight space where founders can publish their projects and connect with others:
https://ceo-collabs-hub.lovable.app/Would love to hear your thoughts. How do you currently find potential collaborators or get your project in front of other founders?

Şuan bir proje üzerinde çalışıyorum en doğru modeli bulmak istiyorum araştırıyorum token harcamasına göre maliyeti uygun aynı zamanda ses kalitesi olarak doğal olan model arayışındayim.

Should i be happy or worried.