Long post, because this thing got a little out of hand.

TL;DR: I built an email marketing operating system that handles almost the entire workflow, from client onboarding and monthly strategy to drafting, revisions, design handoff, segmentation and scheduling. At one point it helped me manage up to 16 client accounts at the same time while cutting a lot of repetitive operational work.

Over time I built an workflow around almost the entire email marketing delivery process.

At this point it handles almost everything from onboarding a new client to having approved scheduled campaigns.

The only production step that still remains manual is the actual email design, although I’m already working on that.

The reason was simple. I was managing a lot of accounts at once and the bottleneck wasn’t writing copy, but keeping all the context, rules, approvals, products, offers, reviews, segments and campaign logic in my head, so I started turning all of that into a system.

What the workflow actually does

- Client onboarding
Scrapes the client website, builds the brand guide, product catalog, current offers, product descriptions, reviews/social proof, links, pricing and other brand-specific knowledge.

- Monthly brief
I input whatever the client gives me for the month. Detailed brief, a few product priorities, a promotion, launch, or even nothing.

- Strategy
Checks previous campaigns and performance (connected to ESP), historical angles, subject lines, products, current offers, holidays, seasonal relevance, previous months’ drafts and what has already been pushed recently.

- Product + angle selection
Chooses products and messaging angles based on historical performance, seasonality, offer relevance, product context and the rest of the monthly campaign plan.

- Drafting
Creates the monthly email drafts using the strategy, brand guide, product data, offers, real customer reviews and client-specific copy rules.

- Client review
Exports the drafts into a normal human-readable format for client approval and feedback.

- Editor / revisions
Takes client comments, changes only what needs changing, and re-checks the updated email against all brand and copy rules.

- Design handoff
Creates/updates task management system and sends approved copy to the correct designer.

- Designed email review
Pulls the completed ESP drafts and creates a client-facing table with web-view links for review.

- Corrections
If the client requests visual changes, the workflow routes the feedback back to the designer through task management system and brings the campaign back into review once completed.

- Segmentation + exclusions
Applies client-specific audience rules, target segments, engagement windows and exclusions.

- Follow-ups, campaign variants or different types of sending
Duplicates campaigns when needed, creates follow-up sends and prepares different audience versions. Can send first to the most engaged audience, then progressively broader segments while excluding everyone already targeted in previous tiers.

- Scheduling
Once approved, schedules the campaigns through the API using the client-specific sending rules.

So the actual flow is basically:

brief > strategy > drafts > client review > revisions > design > review > corrections > segmentation > scheduling

Under the hood this became pretty big.

There are a lot of scripts, skills, markdown files, APIs, client-specific rules and handoffs behind it.

At some point it stopped feeling like a bunch of automations and started feeling more like an email marketing operating system.

Generating copy is easy. The harder part is knowing what was previously sent, what performed, which product makes sense currently, what offer is active, which review supports the message, how the brand talks, who should receive the email, who needs to be excluded, what the client approved and what still needs fixing.

The impact on my workload was pretty significant. New client onboarding went from a working day to roughly 30 minutes. Creating around 8 monthly email drafts for an established client went from roughly 3–4 hours to around 20 minutes for the initial draft set.

But the biggest result was capacity. At one point I was managing up to 16 client accounts simultaneously, because most of the repetitive operational work was no longer being done manually.

For me, the breakthrough was turning a large part of the delivery process into a system. That’s what actually created leverage. I got less repetitive work, more capacity, and fewer things falling through the cracks.

I've spent 10+ years around fundraising deals, and the pattern repeats: founders raise because it feels like the next step, not because the business needs it yet.

Here's what raising too early usually costs:

• You sell 20% of your company when it's worth the least

• You start reporting to investors before you know what works

• You feel pressure to spend fast instead of learning fast

• Your next round has to justify a valuation you haven't earned yet

Meanwhile, founders who wait until they have real customers and some revenue often raise less, give up less, and negotiate from strength.

That doesn't mean never raise. Some markets reward speed, and capital buys speed. But "everyone else is raising" isn't a reason.

My rule of thumb: raise when money is the only thing standing between you and a clear next milestone. Not before.

So, two questions:

1. Founders who raised early: was it worth it, or do you wish you'd waited?

2. Founders who waited: did it make the raise easier?

Curious where this community lands.

So, i have done previous posts here where i discussed the subscriptions i have to promote my product.
I also got a few users from x and linkedin premium i used for networking.

Now, I am getting Zero results from Meta ads. All I got something was from SEO for which i used pilotdeck but the problem is it can't be amplified, spoke to their team but they only provide max 30 human written blogs a month. Shall i hire a freelancer and create bulk pages for SEO? Or if not SEo than what other platform shall I use to run ads? Reddit or linkedin ads.

My product is into parenting.

I recently had the pleasure of spending two weeks in SF for Tech Week and Disrupt. I got to meet a lot of incredibly bright people and had a lot of fun seeing the startup scene on the ground level. The one thing that I caught wind of was the amount of larping going on from within these 'prestigious' incubators.

So what are they doing?

Well, they basically all sell to each other and then post about it all over X and in their pitch decks flexing their ARR. I buy 30 seats of your SAAS at $25/seat and you buy 10 of my seats at $75/seat. Net result - we just got $9k+ of ARR. Nice!

I thought, hey everyone should have access this!

Put a credit card in with a spend limit, and do instant swaps of ARR from one business card to another (or many)

Anyways, curious what you all think of this activity or the other stuff that people don't really talk about in the startup world

Context: B2B tool, week one after launch. 18 sign-ups, 7 completed setup, 5 used it, 1 came back.

Traffic is back to baseline after the launch spike.

My first-principles answer is "fix activation first": every new visitor today leaks at the same step, so reach just makes the leak bigger. The counter-argument I keep hearing is that 18 is too small a sample to optimise a funnel on, and you need volume before the data means anything.

For those who've been here: which did you do first, and what number told you it was time to switch?

Hey everyone!

Although I've been involved in software development for a while, I wouldn't even consider myself a junior developer, since I've never had a proper job in the field (apart from a paid, part-time university project).

Over the past few months, I've been developing a web app and a mobile app. They're two different products, but they're complementary to each other. Along the way, I've been learning the fundamentals of Flutter, FastAPI, and SQL, as well as software development concepts, particularly those related to mobile development.

At this point, I'd estimate the project is around 60–70% complete. However, I've built almost everything the old-fashioned way: learning as I go and writing the code myself. My use of AI has been limited to free plans and web-based interfaces. I mainly use AI as a learning tool. I spend a lot of time discussing things with it, and whenever it generates code, I make sure to read, understand, and review everything. At the end of the day, everything goes through my hands.

My original plan was to start relying much more heavily on AI after finishing the MVP. However, given how far AI has come, I'm wondering whether I should change my approach now rather than later.

On the one hand, I could keep developing the way I have been so far, strengthen my fundamentals, and maintain control over the codebase. On the other hand, I could start using AI tools much more intensively, delegate a significant portion of the implementation, and focus on finishing the product and launching it as soon as possible.

I estimate that completing the remaining 30–40% would take me around four months with my current approach. By leveraging AI much more heavily, I might be able to cut that down to just one month.

My concern is that by accelerating development this way, I might lose some control over the codebase and miss out on learning fundamentals that I still need to master.

What would you do in my position? Would you stick to a more traditional approach until the MVP is finished, or start working much more intensively with AI right now? How would you strike a balance between learning to code properly and taking advantage of tools that can dramatically speed up development?

About 1 year and 7 months ago, I started my journey as a solo developer, hoping to eventually turn it into a sustainable business.

Since then, I've shipped 9 products, earned roughly $3,000 in total revenue, and still have no MRR.

What kept me going was the occasional validation. One product was featured by MacStories, the kind of coverage that could've changed an indie developer's life a few years ago. For me, it barely moved the needle.

As revenue wasn't enough to sustain the business, I turned to freelance and contract work to keep things afloat. I've had discussions around $5,000+ contracts, some coming painfully close to closing before falling through.

Every time I considered quitting, something gave me hope. Just enough validation to keep going, never enough to make it sustainable.

I know I can build and ship software, but financially, I have very little to show for nearly two years of effort.

I've considered getting a job, but the tech market feels worse than ever, especially without traditional employment experience.

I still believe something could click. I'm just not sure how much longer I can afford to keep trying.

For those who've been here, what eventually changed things?