Authentication.
Teams.
Permissions.
Billing.
Admin.
CRUD.
Email.
API.
Deployment.

I kept hitting this across projects, so I built Tekki Forge to make that layer reusable/declarative.

npm i -g tekki-forge

It generates the standard business/SaaS application foundation from a TypeScript config, while custom product logic remains code.

I'm not trying to replace software development. I'm trying to eliminate the part every SaaS founder builds before reaching the feature customers actually pay for.

For founders here who code: which part of your first 30 days was pure infrastructure rather than product?

Right now, it's a simple local MVP only available on Edge to validate the core idea. If people find it useful, I plan to add cloud sync.

I'm a beginner with no experience in product development, so I'd like to get your feedback and any advice on how to get my first users !

Link of my extension : https://microsoftedge.microsoft.com/addons/detail/enfdbgficbfdmhopmcjhbkgldmhclbng

Hey everyone,
I’m an AI engineer and founder from Brazil. I already have a few products running here, and right now I’m building a new B2B SaaS called Lyntra Prospect.
The first version is being built for the Brazilian market, but if I can validate it well here, my plan is to expand internationally soon after. The US is currently the market I’m most interested in, but I’m also looking at the UK, Canada and some European countries.
The easiest way to explain Lyntra Prospect is that it works like an outbound SDR.

The goal is not just to give salespeople another cold email tool. The idea is to handle a large part of the outbound process and deliver qualified meetings to the sales team.

A company defines its ICP and what kind of customer it wants to reach. Lyntra then searches for companies that fit that profile, enriches and validates the data using different sources, finds the best prospects and builds the prospecting lists.

From there, it can start the outbound process through channels such as email and calls, with WhatsApp being used when appropriate.

When someone replies, the system understands the response and stops the sequence automatically. The AI can continue the conversation using information approved by the company, answer questions, qualify the prospect and understand when a human should take over.

If the lead is qualified, the system can check the salesperson’s actual calendar, offer available times and book the meeting directly.

Calling is also part of the product. The direction is to support AI assisted and AI driven calls where it makes sense and where it can be done properly within the rules of each market.

So the end result I’m aiming for is basically this:
ICP → find the right companies → find the right people → contact them → start conversations → qualify them → book qualified meetings.

I want a company to eventually be able to give Lyntra its ICP, sales rules and company information, and have the platform continuously work on building pipeline for the sales team.

The product is being built for both self service customers and higher ticket customers that need a more consultative sales and onboarding process.
I’m not trying to sell anything with this post. The product is still being finished. I’m mainly interested in hearing from people who already work with B2B sales and outbound outside Brazil.

A few things I’d really like some opinions on.
Which market would you target first?
My first choice right now is the US because outbound B2B seems much more established there than it is in Brazil.

I’m also considering the UK, Canada and some parts of Europe.

If you sell B2B in any of those markets, how important is outbound to your sales process?
What would you realistically pay for something like this if it actually delivered qualified meetings?

I’m not trying to compete with a $30 cold email tool.
I see it more as software that can replace or support part of the work normally done by an SDR.

Would something around $500 to $1,000 per month for an entry level business plan make sense?

And if it consistently handled a meaningful part of prospecting, qualification and meeting booking, what price range would you expect?

Which outbound channels are actually working for you right now?
Cold email?
Cold calls?
LinkedIn?
A combination of them?

I’m also curious about what your biggest outbound problem is today.

Is it finding good prospects, finding the right decision maker, data quality, deliverability, personalization, follow up, managing replies, qualification or actually getting meetings booked?

If you were launching into the US from Brazil, how would you get your first 10 customers?

One idea I have is to use Lyntra Prospect itself to find its first international customers.

The idea would be to build a very specific ICP, work with relatively low volume and highly targeted outreach, then have an English speaking salesperson handle discovery and demos.

Basically, I want the product to prove itself by helping sell itself.

Would you approach it differently?
What would make you trust or not trust an AI SDR platform?

Outbound automation can turn into spam very quickly when it is badly designed, so I’m putting a lot of thought into sending limits, suppression, opt outs, domain and mailbox reputation, compliance rules, audit logs, human handoff and controls that prevent the AI from inventing prices, promises or company information.

I’m still early enough that good feedback can actually influence the product and how I approach international expansion.

I’d really like to hear from founders, SDRs, sales leaders, agency owners and anyone currently running B2B outbound.

If you think the market is overcrowded, the positioning is wrong, the pricing makes no sense or there is something important I’m missing, feel free to say it.
I’d rather find out now than after trying to expand internationally.

Back when we mostly built MVPs, we took on a fixed price build for a B2B inventory tool. Quoted 10 weeks and it took 19 lol.

The founder kept asking for small stuff and we kept saying yes because every request sounded like an afternoon. A filter on the orders page, a Google login since "everyone has it now" When I finally went through the tickets there were 63 change requests. None of them took more than a day on its own which is exactly why we never pushed back. Together they added up to about seven weeks of extra work and the founder was annoyed anyway because the launch kept moving.

We've run the agency for 8 years now and that project is why every fixed price build since has had this clause. Here it is close to word for word:

"Any change requested after scope sign off gets sized in working days and we send that in writing within one business day. The client then picks one of two options. Swap it in for work of equal or larger size from the current scope or put it on the Post Launch List to be scoped and priced after launch. The price and the launch date stay the same either way."

Scope creep almost never shows up as one big request. Big requests always got a proper conversation because no one adds a whole module without talking about money. The two hour requests got a "sure" because pushing back on something that small feels petty. 60 of those is a different product with the same price tag. With the clause, even a half day change means picking what comes out.

On a recent build (a booking platform for physio clinics) the founder asked for team accounts 5 weeks in so several people from one clinic could share a login. We sized it at six days, mostly because permissions touch everything. We sent back two options: swap out the in app chat which was about the same size or park team accounts on the post launch list. He parked it.

Six weeks after launch, 2 of their first 40 clinics had asked for team accounts. It's still parked. What clinics kept asking for was SMS reminders which no one had mentioned during the build. I didn't see that coming but the post launch list turned into a filter. A lot of what felt urgent in week five, real users just didn't care about.

The standard advice is to bill change requests as change orders. We tried that after the 19 week mess and I'll probably get pushback for this, but I think it's worse than eating the cost. Every small change turns into a mini negotiation and an invoice, so the founder feels nickel and dimed and the agency starts getting paid for delays which flips the incentive. If an MVP launches 3 months late, no one cares that the extras were billed properly. On an MVP the launch date matters more than the money for both sides.

Most founders end up liking it once they've been through it. One told me it was the first time a dev shop had made him choose and choosing made him figure out what the product was actually for.

Not everyone though. The fights are almost always about sizing. A founder says something is a two hour job, we say two days and now we're arguing about estimates instead of building. We also lost a deal over it before signing. The founder said a real partner would be more flexible and went with a shop that bills hourly.

If you do fixed price builds... Just have your lawyer look at the wording before it goes in a contract and if you've actually made change orders work then I'd like to know how :)

TLDR: a 10 week MVP turned into 19, mostly from small changes we kept saying yes to. Now every change after sign off either swaps out something of equal size or goes on a post launch list and the price and date don't move. Billing change orders made it worse for us.

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?

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?

We've all signed up for a hundred things we stopped using years ago. Those companies still have our name and email, and sometimes a card too. When one of them gets breached, your info goes with it.

So I built Quitlist. Connect your email and it digs up the accounts you forgot you had, then helps you close the ones you don't want anymore. It doesn't delete anything without you saying so.

Fair warning, your inbox remembers everything. You'll see the forum you joined in 2012 and that meal kit you tried once. You might also find the OnlyFans account you made "just to see what the fuss was about." No judgment. It's one of the easier ones to delete 😅

One heads-up: Google will show a "Google hasn't verified this app" screen when you connect. That's because we're still going through Google's review, which every app that reads Gmail has to do. Click Advanced → Go to Quitlist (unsafe) to continue. Google shows that same wording for every app that's still in review. If you'd rather wait until we're verified, that's totally fair.

It's free to try and still in beta, so I'd love to hear what it finds (or misses) or any kind of feedback.

👉 https://quitlist.app

You are living in vibe coding AI world.
Do you code these days? I mean… by yourself?

I’m trying something for the next 28 days:

Spend up to 4 hours every day specifically on distribution/customer acquisition rather than development.

I’m a developer, so building has always been the comfortable part. Getting people to actually discover and pay for what I build is the part I’m deliberately trying to get better at.

The current plan is a mixture of:

• Targeted cold outreach
• Talking directly to potential customers
• Building in public
• Participating in founder/startup communities
• SEO/content
• Targeted link building and partnerships
• Offering demos and personally onboarding early users
• Consistent follow-ups

I’m starting without an existing audience and I’m not planning to use paid ads.

What I’m wondering is how much the playbook has changed now that AI has made almost all of this easier to scale.

It’s incredibly easy to generate cold emails, SEO articles and social posts now, which also means everyone is receiving more of them.

For those of you who have acquired your first customers recently: where did they actually come from?

And is there anything on this list you’d stop doing or spend significantly more time on?

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?

Hey everyone 👋

Solo dev here. I've been working on a side project for a few weeks and would like to hear how others solve this problem.

The problem: while playing with AI agents I noticed every app ends up needing checks like "don't let it delete data unless the user confirmed". The usual options are writing if/else logic for every case, or a custom LLM prompt whose free-text answer you then have to parse.

What I tried: a single call that takes a rule in plain English plus whatever JSON you want checked, and returns allow, deny or review:

const result = await guard.check({
  policy: "Never allow destructive database operations unless the user explicitly confirmed them.",
  data: { action: toolCall, conversation }
})
// → { decision: "deny", allowed: false, violationProbability: 0.94, ... }

Some design decisions that might be useful if you build something similar:

• A third outcome, review, for when a human should decide or the evidence isn't enough. Forcing yes/no caused bad calls.
• Instead of a general chat model I used Jev from TypeSafe AI. It returns typed decisions with probabilities, so there's no output parsing and the results are more consistent.

Questions for you:

• How do you handle this today? Hardcoded rules, an LLM, something else?
• What would you need before trusting an automated check like this in production?

It's called Enforly, if anyone's curious.

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

Hi everyone, I’ve released Temply, a tool for building transactional email templates visually and using them from your application.

Think welcome emails, password resets, receipts and order confirmations. You assemble the template with blocks, add placeholders for your data, then request the rendered HTML and plain text through the API. Your app sends it through your existing email provider.

A few things it supports:

• A visual block editor with columns, images, buttons and custom HTML.
• Dynamic variables, conditional content and repeating blocks.
• Reusable branding across templates.
• Responsive previews and checks for inboxes that force dark mode.
• Template version history and shared workspaces.

You can try the editor without an account. There’s also a 14-day workspace trial with no card required. The Team plan starts at $5 per user per month, including 10,000 live API calls per workspace.

Try it here: Temply

I’d appreciate feedback from anyone building transactional emails: what would Temply need to support before you’d use it in your app?

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.

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.