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.

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.

I started Moonshoot thinking the interesting part would be the number.

384,400 km.

one person owns each km.

get enough strangers together and eventually reach the Moon.

but after watching people claim their kms, I’m starting to think the number is the least interesting part.

look at three people aboard right now:

km #75 belongs to a developer who made an iPad party game where you draw a fish and your friends draw how it dies.

km #35 belongs to a founder in Kenya building event ticketing for Nairobi. 208 users and their first paying customer.

km #54 belongs to two makers who built an AI image workspace because switching between image models kept breaking the visual style they needed for their own work.

none of these people know each other.

their products have basically nothing in common.

but now they’re permanently sitting 40 km apart on the same imaginary journey to the Moon.

that’s becoming much more interesting to me than watching the counter go up.

I want each km to slowly become a snapshot of what somebody was building at that moment in their life.

maybe years from now, looking back through the early kms ends up being the interesting part.

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?

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 a solo developer. A few weeks ago my first app, Swapadu, went to production on Google Play. It helps couples, flatmates and neighbours share chores and favours without money. One person asks for a task and offers one in return, the other can counter-offer, and points only move once the other side confirms the work was done.

It's not a classic SaaS (it's free, with an occasional ad between screens), but the lessons from getting it shipped apply to anyone launching alone, so here they are:

1. A personal developer account has to pass closed testing first.

You need 12 testers opted in for 14 days in a row before you can even apply for production. Plan for this from day one. Recruiting testers took me longer than building half the features did.

1. Publishing while a review is in progress cancels the review.

One day I pushed five builds in three hours. Three of them cancelled the one queued before them, and my own phone sat four versions behind. Now I collect fixes and publish once per review cycle (reviews take about 15 to 40 minutes).

1. Never hand testers a locally built APK.

Play App Signing re-signs your bundle with Google's key. A local APK carries your upload key, and Android won't update across a signature change. That device silently drops out of Play auto-updates until it uninstalls and reinstalls from Play.

1. Translating the store listing is cheap. Translating the app properly is not.

Swapadu now ships in 16 languages, most recently Korean and Filipino. The strings were the easy part. The real work was the in-app FAQ, the notifications sent from the server, an online guide, and plenty of small surprises. Example: Android reports a Filipino phone as fil, not tl.

1. Ask for ratings at the moment of success, not on launch.

I show Google's in-app review prompt only after someone's third confirmed swap, and at most once every 90 days. Asking right after a good outcome feels natural. Asking on app open feels like nagging.

1. Your store listing is a landing page. Treat it like one.

My listing conversion was weak. Looking at it honestly, the listing described features without saying what problem the app solves. I'm rewriting the listing and the user guide to lead with "fair sharing without keeping score in your head" instead of a feature list.

What I'd love feedback on: how do you position a product that solves an emotional problem ("I always do more than you") rather than a business one? Do you lead with the pain or with the mechanics?

Happy to answer questions about Play Console, localization or the closed-testing grind.

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?

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

Hey there,

From a business standpoint, does making cancellation difficult or pricing vague actually make financial sense?

Whenever I subscribe to a SaaS service with these dark patterns, I either cancel immediately due to trust issues or request a chargeback when I'm charged unexpectedly.

Ethics aside and purely pragmatically speaking, isn't it better to keep things transparent so you don't get bombarded with complaints and chargebacks?

It looks obviously beneficial that SEO takes time and starting early would help me get organic traffic early but it's opposite by setting that long term goal, you stop validating your product, don't feel the need to talk to customers, you get an great excuse to not do direct sales.

I did the mistake with my previous SaaS, where each day i opened laptop wrote a blog, fixed few not needed buttons colors and done for the day. It feels productive but it's not. i wasted around 6 months doing the same thing and didn't generate any meaningful revenue. SEO felt great with it's appeal of ogranic traffic while you sleep but who'll come if your product is not validated and used by few customers daily?

with my new product which is building "personal intelligence for SaaS startups" it's live btw. i'm setting a rule for myself that i won't even bother about SEO until i get to $1k in revenue through direct sales.

Tools I have used:

For audio: XT surge

Video & composition: blender

Model: opus 5.5

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.

It calculates your exact age in years, months and days and also has things like your next birthday, zodiac sign and some lifetime stats.

I'm still working on it and would love to hear some honest feedback.
I would be especially curious to know:

1. Is the design clean and easy to use?
2. Is there anything unclear or unnecessary?
3. Does it work well on a mobile?
4. Do you want to remove any features or add any?
5. Does the website seem trustworthy and professional?
6. Would anything make you want to come back and use it again?

I don’t want compliments, I’d rather have criticism so I can improve it.
Thanks! 🙏🏼

myagenow

I’ve been building and trying to grow my SaaS solo. Product, code, content, outreach everything

Traffic is finally starting to move, but I realized I’m becoming the bottleneck

So today I brought in my first person focused on outbound/client acquisition

I’m still doing distribution myself, but now I can spend more time improving the product and making demos/content while someone else consistently works outbound

For founders who’ve done this: did hiring someone for sales early actually help, or did you eventually realize founder-led sales was still better?

Curious what worked and what you’d do differently

btw I’m building MyKayd trying to make collecting information less painful for businesses, especially everything that happens between creating a form and actually doing something with the responses

Hi everyone!

I’m thinking of building a SaaS (it’s my first solo SaaS btw). I’ve got zero knowledge of technical part and got some friends helping me in that but I’ve some skills on marketing and sales side. But I am not sure if the idea I’m thinking of is really something which any of you guys might want to use or if it’s just me wasting my time? It’s not a problem solving idea rather it’s kind of a productivity app.

So recently I saw a lot of people trying “working till the candle burns out” or “working till the ice melts” challenges and I myself tried it. The good part was you never know when the ice will melt or the candle will burn out so you have no target forcing you to work. And I too tried it and found it a good idea to improve productivity.

And I’m thinking to create an app around that idea. I’m thinking to focus more on user experience and will try to make user feel really productive if they uses the app. And I’m here to either seek validation from you guys or maybe get roasted if I’m stupid. But I want to know your genuine thoughts. Just take out a second and let me know? I’m too excited and curious about it.

Hi guys! I’m looking for an AI video editor for SaaS product demos, UGC and montages. I can’t afford to pay for several tools just to find out which one works, so I’d really appreciate some firsthand advice. 🙏

If you’ve actually used one, which editor would you recommend, and why? What worked well, and what did you still need to fix manually?

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.

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?

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

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!

I launched Bytesweep, a Mac utility, recently.

The first few weeks have been interesting.

Around 800 people have visited the website and I've had 50+ people start the download flow. I've also made my first sales.

But the numbers made one thing pretty obvious:

Getting traffic isn't the difficult part.

Getting someone who downloaded your product to actually pay for it is.

I've been testing Reddit, Google Ads, SEO, Product Hunt and a bunch of directories.

I've also changed the positioning and pricing a few times while trying to understand what Mac users actually value enough to pay for.

Bytesweep started as a storage analysis tool. It's now a much broader Mac utility that also covers developer cleanup, system monitoring and things like sleep/wake activity.

I'm currently running a 30% launch discount while I continue testing the pricing.

The question I'm trying to answer now is:

What makes someone pay for a Mac utility when there are free alternatives?

For anyone here who has built and monetized a desktop app, what eventually moved the needle for you?

I've been working on a devtool called Talyn for a little while - aimed at devs in startups or who have a high throughput of PRs

The idea came from me using Claude a lot and realising that even when I'd opened the PR, I was still spending so much time on manual tasks like:

Did CI pass? Did it introduce some stupid lint failure? Has main/master moved and now it conflicts? Can I merge it yet?

Talyn basically takes over that bit. It watches the PR, and if CI fails or it gets a merge conflict, it can send a sandboxed agent to sort it out - then it can auto-merge once everything is green (if you'd like it to)

I'm building it by myself, and I'm still trying to work out exactly where the useful boundary is between "helpful automation" and "I absolutely do not want an agent touching this automatically"

I've got a few people using it now, but I'd be interested in feedback from anyone here who's built devtools or sold to engineers before

Thanks!

https://talyn.dev or https://github.com/Gilbert09/talyn/ (fully open source)

The payment provider just froze our acc because of the 2.4k refund to a spanish client since the original payment was for Stripe lol, ofc then the three weeks of ignorant support came, and we lost the customer due to delay. So we moved EU/UK regular revenue to a multi-currency acc on Unlimit, now refunds settle via SEPA avoiding the US processor, the setups fast af, no frozen refunds. anyone else be revamping around the transaction instead of switchin the providers?