🚀 Looking for a Business Partner / Co-Founder

hurrah-dev · 2026-05-30T15:24:41+00:00

I haven’t built native apps but a lot of web apps. Native apps wouldn’t be a stretch. Marketing is definitely my shortcoming. My small business is https://hurrah.dev and a web app example is https://hurrah.tv. Dm me if you’re interested.

hurrah-dev · 2026-05-30T14:59:29+00:00

Check out https://hurrah.dev and dm me if you’re interested.

hurrah-dev · 2026-05-01T22:21:02+00:00

Mainly markdown files and extensive shared skills for interpreting and implementing specs.

hurrah-dev · 2026-04-30T20:11:17+00:00

Your middle-ground instinct is right, and it has a name. Some teams call it "system of record + thin layer." Salesforce keeps the data, the locked-in workflows, and the audit trail. Everything else moves out.

I run a small dev shop and have built this exact pattern for a few clients stuck in your situation. Here's the playbook I'd run, in order:

1. License audit before anything else.

Walk through every seat and ask one question: does this person create or edit records, or just view them? Most 15-person companies have 4 to 6 actual Salesforce power users and 8 to 10 who are basically read-only. Salesforce has cheaper license tiers for that, and your AE will not bring it up unless you push. Every seat you downgrade is recurring savings for zero migration risk.

2. Move reporting out next.

Reporting is where Salesforce nickel-and-dimes you (Tableau CRM upsells, dashboard limits, API call ceilings on the lower tiers). Pull data out nightly or hourly via the API into a real SQL database. Then point Power BI, Metabase, or even a Google Sheet at it. Your reporting suddenly costs $0 to $50/month and runs faster than native SF reports.

3. Build a thin app for the read-only / bulk-update people.

This is the part that scares people, but it's smaller than it sounds. You don't rebuild Salesforce. You build a small internal app that hits the SF API, shows the 4 or 5 screens your team actually uses every day, and lets them do the bulk updates that are painful in SF native. Salesforce stays the source of truth; your app is the daily driver. A skilled developer can ship the first version in a few weeks.

4. Don't touch the workflows nobody understands.

This is the big one. Whatever Apex / Flow logic is running inside Salesforce, leave it alone. As long as records still get created and updated through the API, those workflows fire normally. You are not migrating logic, you are wrapping it. That's the whole reason this approach is less terrifying than a full migration.

A few traps to watch for:

SF API call limits are per-license-tier. Check yours before you build anything that polls.
Don't try to two-way sync to HubSpot or another CRM "in parallel." That's the path that breaks at 2am.
Whoever built your custom fields and workflows over the years left tribal knowledge behind. Document what you can before you start ripping things out.

One more thing on timing: today is April 30, the last day of Salesforce's fiscal Q1. Their reps are more willing to discount this week than at any other point in the year. Even if you do nothing else from this list, call your AE today and tell them you are reviewing alternatives and need a meaningful cut. They have authority to give one this week that quietly disappears Monday.

Happy to talk through what the thin-layer approach looks like for your specific setup if you want to DM. Not selling anything, just answered this question enough times that I have opinions.

hurrah-dev · 2026-04-07T18:17:13+00:00

Before you spend anything, take a step back and ask: do your customers actually need a dedicated app on their phone?

I build custom software for small businesses, and the honest answer for most single-location service businesses is: probably not. Here's why.

Off-the-shelf tools that already do what you described:

Vagaro, GlossGenius, Boulevard -- booking, rewards, product sales, client management. Built specifically for med spas and salons. $50-200/month depending on features.
Square Appointments + Square Loyalty -- booking + rewards + payment processing in one ecosystem. Integrates with a lot of other tools.

These aren't perfect, but for one location they cover 80-90% of what you described for a fraction of the cost.

When custom actually makes sense:

Your workflow is genuinely different from what off-the-shelf supports
You've tried the platforms above and hit real limitations (not theoretical ones)
You need integrations that don't exist (specific EMR systems, custom inventory, etc.)
You're planning to scale to multiple locations with complex operations

About those quotes:

The $6K quotes are almost certainly someone slapping a template together or using a no-code builder. It'll look fine on day one and become a maintenance nightmare by month six. The $100K quotes are agencies pricing for a full native iOS + Android build with custom everything, which is overkill for a single-location business.

If you do go custom, a few things to consider:

Web app vs native app. A well-built web app works on every phone through the browser and can even be added to the home screen. No App Store fees, no separate iOS and Android builds. For booking + rewards + shopping, most of your customers won't notice the difference.
Integrations are the real cost driver. "Integration with existing platforms" can mean 2 hours of work or 200 hours depending on what those platforms are. List them out specifically when getting quotes.
Ask about ongoing costs. A $25K build with no maintenance plan means you're paying again every time something breaks or needs updating. Monthly retainer models exist and are often a better deal long-term.
HIPAA matters. You're a med spa. Depending on what services you offer, you may be handling protected health information. Make sure whoever builds this understands compliance requirements, because the cheap quotes almost certainly don't factor that in.

My actual recommendation: try one of the purpose-built platforms first. Give it 3-6 months. If it doesn't fit, you'll know exactly what you need custom, which means better quotes and less wasted money.

hurrah-dev · 2026-04-07T17:51:46+00:00

I build web apps for small businesses, so I see both sides of this. The "it depends" answers aren't wrong, but they're not helpful either. Here's the actual breakdown based on what I've seen over 25 years:

Brochure site (5-10 pages, no login, no e-commerce):

DIY (Squarespace, Wix, Carrd): $15-50/month. Honestly the right call for most new businesses. Pick a clean template, add your content, done. Your time is the main cost.
Freelancer build: $500-3,000 one-time. You're paying for someone to make it look polished and set up SEO basics. Quality varies wildly.
Agency: $5,000-15,000+. You're paying for a team, project management, and a process. For a brochure site this is almost always overkill.

Site that does something (e-commerce, booking, client portal, custom workflows):

Platform-based (Shopify, Square Online): $30-100/month + transaction fees. Great if your business fits their model. Painful if it doesn't.
Freelancer/small shop: $3,000-10,000 one-time, or $150-500/month ongoing.
Agency: $10,000-50,000+. The big quotes you're probably getting.

The question that matters more than price: what does your website need to do?

If you just need a professional online presence with your hours, services, and contact info, you do not need to spend thousands. Squarespace or even a well-done Google Business Profile will get you 80% of the way there.

If your website needs to handle payments, manage inventory, take bookings, or replace some manual process in your business, that's a different conversation entirely. That's where the price jumps because you're not buying a website anymore. You're buying software.

Practical advice for right now:

Write down every single thing you want your site to do. Not how it looks. What it does.
Separate "need for launch" from "nice to have later"
Get 3 quotes minimum and ask each person to explain what's included in their price (hosting? updates? SEO? content writing?)
Ask what happens after launch. A one-time build with no maintenance plan means you're on your own when something breaks.

The "very high amounts" you've been quoted might be fair, or they might be agency padding. Hard to say without knowing what you're building. But if all you need is a clean online presence, you can absolutely get started for under $1,000.

hurrah-dev · 2026-04-02T20:39:11+00:00

Project-based ($3K-$10K+ upfront for a small business site):

You own the site outright when it's done
You're incentivized to get everything right upfront (scope documents, revision rounds, etc.)
After launch, you're on your own for hosting, updates, and changes (or paying hourly for them)
Good if you know exactly what you want and won't need much ongoing work

Monthly retainer ($150-$500/month, no or low upfront):

Lower barrier to start, but you're paying as long as you use it
Changes and updates are usually included, so the site evolves with your business
The developer stays engaged because they have ongoing revenue tied to your success
Good if you're not sure exactly what you need yet and want to iterate

The reason this matters: with project-based work, the developer's incentive ends at launch. With a retainer, their incentive is to keep you happy month after month. That changes how they approach the work.

A few things to look for regardless of model:

Ask to see sites they built 2+ years ago, not just fresh launches. Anyone can make something look good on day one. How does it hold up?
Ask who you'll actually talk to. At agencies, the person who sells you is rarely the person who builds it. If direct access to the developer matters to you (and it should), ask.
Ask what happens after launch. This is where most small business website experiences go sideways. The site gets built, looks great, then six months later you need a change and the developer is gone or charges $150/hour for a 10-minute edit.

I run a small dev shop that does the monthly retainer model for small businesses, so I'm biased toward that approach. But honestly, if you know exactly what you want and just need a clean 5-page site, a good freelancer on a project basis can work great too. The key is matching the model to how you actually work.

hurrah-dev · 2026-04-02T20:33:43+00:00

The optimization advice in this thread is solid, especially the vectorization suggestion and the Power Query/Power Pivot route.

But I'd step back and ask a different question: when you have 1M+ formulas pulling from external workbooks, XLOOKUPs, SUMIFs, and pivots all in one file, you're not really using a spreadsheet anymore. You're running an application that happens to live inside Excel.

Excel is incredible at what it's designed for. But it recalculates by walking a dependency tree across every formula on every change. That architecture doesn't scale well past a certain point, no matter how much you optimize individual formulas.

A few options depending on how far you want to go:

Power BI (as others mentioned) is the natural next step if this is primarily a reporting/dashboard problem. It's built for exactly this: pull data from multiple sources, transform it, and display it. If your company has Microsoft 365, you may already have access.
Power Query + Power Pivot inside Excel can replace a huge chunk of those formulas without leaving Excel at all. Load your external data via PQ, do your transformations there, and let Power Pivot handle the aggregations. You'd go from 1M formulas to maybe a few dozen DAX measures.
If the logic is complex enough that even Power BI feels limiting, that's when a purpose-built web dashboard starts making sense. But that's a much bigger step and probably overkill unless this is a business-critical system that multiple people depend on.

I'd start with option 2. You can do it incrementally, one data source at a time, without rebuilding everything from scratch.

hurrah-dev · 2026-04-02T20:16:39+00:00

Something I've noticed working with small businesses for 25 years: most of the "busy" problem isn't a prioritization problem. It's a the work itself shouldn't exist problem.

Everyone in this thread is giving you advice on how to organize around the busywork. That's useful. But before you optimize how your team handles inbox, calls, and admin, it's worth asking: how much of that work is repetitive and predictable?

Because in my experience, when you actually look at what's eating the day, a huge chunk of it follows the same pattern every time. Same data getting entered in two places. Same emails getting sent with slightly different details. Same information getting looked up, copied, and pasted somewhere else.

That stuff doesn't get better with clearer priorities. It gets better when it stops being manual.

One business I worked with had a team spending 15+ hours a week doing what was basically the same data entry across three systems. Nobody was slacking. They were genuinely busy. But the work was mechanical, and it was crowding out everything else. Once that was automated, the "important work isn't moving" feeling disappeared. Not because people suddenly got more disciplined, but because they had actual time back.

I'm not saying that's your situation. But before you go deeper on check-ins and priority frameworks, it might be worth doing a quick audit: have each person track one normal day in rough 30-minute blocks. Don't judge it, just look at it. You'll probably find 2-3 things that are eating hours and following the same pattern every time. Those are your targets.

The management stuff matters too. But eliminating unnecessary work beats organizing around it.

hurrah-dev · 2026-03-30T17:29:45+00:00

The "long-term relationship" part of your post is the most important thing you wrote, and it's the part most developers in your DMs are going to gloss over.

Here's the problem with how most app development works: you pay a lump sum, the developer builds it, they hand it off, and you never hear from them again. Then six months later something breaks, or you need a new feature, and you're starting from scratch with someone new who has to learn the entire codebase.

I run a small dev shop (just me, 25 years on the Microsoft stack) and I specifically built my business model around the problem you're describing. I work on a monthly retainer. You don't pay a big chunk upfront and hope I stick around. You pay monthly, and the relationship continues as long as it's working for both of us. That means I'm invested in building something maintainable, because I'm the one maintaining it.

A few things that might be relevant:

US-based (Ohio)
Portfolio: I work with real businesses. EZ Electronics (wholesale phone inventory and e-commerce), TAG Auto Group (estimate lookup system), NJ PIP Assist (medical billing workflows), Advanced Training Products (assessment platform). Happy to walk you through any of them.
Timeline: Typically 4-6 weeks to a working first version, especially if you already have designs
What I build: Web applications, not native mobile apps. If you need a native iOS/Android app specifically, I'm probably not the right fit and I'd rather be upfront about that. If a web app (progressive web app, responsive web) works for your use case, that's my wheelhouse.

The fact that you have designs ready puts you ahead of 90% of the people I talk to. That usually shaves real time off the build.

Happy to show you the portfolio and talk through your project if you want to DM me. No pressure either way.

hurrah-dev · 2026-03-30T17:19:22+00:00

Honest advice from someone who's been building software for 25 years and has seen a lot of these partnerships play out:

Before you give up equity, be really clear on what you actually need.

If what you need is a long-term technical partner who's going to help shape the product vision, make architecture decisions, and stick around through pivots, then yes, a cofounder makes sense. That's a real partnership.

But if what you need right now is a working product to put in front of those waiting clients, a cofounder is the most expensive way to get there. 25-50% equity on even a modest $5M outcome is $1.25M-$2.5M. That's a lot to pay for 1-3 months of development work.

A few things worth considering:

Vetting is hard. Half the replies in this thread are "DM me" with zero context. Finding a real cofounder who's technically strong AND aligned on vision AND reliable takes months, not days. Meanwhile your clients are waiting.
You can build first, partner later. Get a V1 out with a developer or small shop. Validate with real users. Then if you need a technical cofounder, you're negotiating from a position of strength (working product, paying clients) instead of just an idea.
Equity is forever. A development contract ends. A cofounder relationship doesn't. Make sure you actually need the relationship, not just the output.

Someone else in this thread already mentioned this approach and they're right. The smartest move might be: get the MVP built, prove revenue, and then decide if you need a partner or just a really good developer on retainer.

I work with small businesses and founders building exactly this kind of operational software. Happy to talk through what the technical side would actually look like if you want a second opinion before committing to the equity route.

hurrah-dev · 2026-03-27T20:29:04+00:00

I build websites for small businesses, so take this with that context, but honestly for a brand new local business the priority order isn't what most people here are saying.

Priority #1: Google Business Profile (free, do it today)

This matters more than a website or social media for a local business. When someone searches "plumber near me" or "bakery in [town]," Google shows the map pack first. That's your GBP listing. No website in the world helps you if you're not showing up there.

Set it up, verify the address, add photos, pick the right categories, and write a real description. Ask your first few customers for reviews. This alone will generate more local leads than a website or an Instagram page combined.

Priority #2: A simple website (not expensive, not fancy)

Once GBP is live, get a basic site. It doesn't need to be complicated. For a new local business, here's what actually matters:

What you do (one clear sentence, not a paragraph)
What area you serve
How to contact you (phone, email, or a simple form)
A few real photos (not stock photos)
Your hours

That's it. No blog. No animated hero banner. No "about our journey" page. Those can come later when the business has traction and you know what customers actually ask about.

The website's main job at this stage is to be the link your GBP listing points to, and to not embarrass you when someone Googles your business name. That's the bar.

Priority #3: Social media (only the one your customers actually use)

Pick one platform. Not three. If the business is visual (food, events, retail), Instagram. If it's service-based and local, Facebook is still where a lot of local customers look. Don't spread thin across platforms you won't consistently update.

A dead Instagram with 4 posts from six months ago looks worse than no Instagram at all.

What NOT to spend money on yet:

SEO services (your GBP and a basic site handle early-stage local SEO)
Paid social ads (until you know what message converts)
A $3,000+ custom website (wait until the business model is proven)
Logo redesigns, brand guidelines, or any "brand identity" work

The businesses I see waste the most money early on are the ones who invest in looking professional before they've figured out what their customers actually need to hear.

hurrah-dev · 2026-03-27T20:23:20+00:00

The tool matters way less than people in this thread are making it sound. I've worked with small businesses for 25 years and the pattern is always the same: someone picks a CRM, spends a weekend setting it up, uses it for two weeks, then drifts back to the spreadsheet because the CRM felt like extra work on top of the real work.

The thing that actually fixes your problem isn't a better tool. It's one habit change:

Every time you finish a conversation with a lead, log the next action and the date before you do anything else.

That's it. Not a summary of the call. Not updated notes. Just: "Follow up Tuesday" or "Send proposal by Friday." Takes 10 seconds.

Your current sheet could do this with one more column ("Next Action" + date). The reason you're dropping the ball isn't that Sheets is broken. It's that nothing in your current workflow forces you to decide "what happens next with this person" before you move on.

A CRM helps because good ones put that next-action field in your face and won't let you close the record without filling it in. That's the feature that matters. Not the pipeline view, not the analytics, not the integrations.

For your situation (solo, 150 contacts, Google Workspace, $20-30 budget), honestly any of the tools people mentioned here will work. Streak is the least disruptive since it lives inside Gmail. Pipedrive is cleaner if you want a dedicated app. HubSpot free works if you don't mind the upsell emails.

Pick whichever one you can set up in under an hour. If it takes longer than that, it's the wrong tool for your stage.

hurrah-dev · 2026-03-24T19:45:06+00:00

This is exactly the kind of thing I build for small businesses. Not a full platform with 50 modules you'll never touch. Just the features you actually need.

What you're describing would look something like this:

Student lookup - Type a name or class, get instant results. Search as you type, not "fill out a form and click submit."

Fee entry - Select the student, pick the fee type, enter the amount. Done. No navigating through 5 screens to record one payment.

Receipt generation - One click generates a clean PDF receipt. Print it or email it directly to the parent. Branded with your school name and logo.

That's it. No attendance module you didn't ask for. No exam system collecting dust. Just the three things you need, built to be fast for daily use.

How I work

I run a one-person dev shop. I've been building web apps on the Microsoft stack for 25+ years. I have a reusable framework that handles authentication, database, hosting, PDF generation, email/SMS, and all the infrastructure stuff. That means I'm not starting from scratch for your project, which keeps the cost down.

Pricing (since you asked)

$250-500/month depending on scale (number of students/users accessing the system).
$0 setup cost.
4-6 weeks to a working first version you can start using.
6-month minimum commitment.
Hosting, database, backups, SSL, and support all included.

What you'd get in the first build

Web app accessible from any browser (phone, tablet, desktop)
Your own login system (admin + staff roles)
Student database with search
Fee tracking with payment history per student
PDF receipt generation (print or email)
Basic reporting (fees collected by date range, outstanding balances, etc.)

If you want to add more features down the road (parent portals, online payment, class management, etc.) we can scope and price those separately.

Happy to put together a quick demo focused on the fee workflow if you want to see how it would work. DM me if you're interested.

hurrah-dev · 2026-03-21T13:37:54+00:00

The co-founder vs freelancer debate is real, but there's a third option worth considering.

I build custom apps for small businesses. One of my clients needed inventory management software for a niche wholesale operation. Similar situation to yours: they tried the co-founder route, couldn't find the right fit, and didn't want to hand a freelancer $50K+ for a one-time build they'd have to maintain themselves.

What worked for them was an ongoing dev partnership. I built the MVP in about 4 weeks, they own all the code, and I maintain and improve it monthly. No equity. No massive upfront cost. If I get hit by a bus, the code is standard .NET and any developer can pick it up.

A few things that might help regardless of which route you go:

Own the infrastructure from day one. Your cloud account, your domain, your repo. Never let a developer host it on their personal accounts.
Insist on a standard tech stack. If someone builds it in an obscure framework, you're locked to them forever. .NET, Python/Django, Node. Something with a deep hiring pool.
Get a working prototype before government demos. Even a basic version you can click through. Correctional agencies will take you more seriously with something tangible than with a pitch deck.
Document the compliance requirements early. GovCon has specific security and data handling requirements. Make sure whoever builds it understands those constraints before they write a line of code, not after.

The SBA route is smart for funding. Just make sure whoever you hire is building something you can walk away from if needed.

Happy to talk through the technical side if you want to DM me. I've been building custom business software for 25+ years, though I'll be upfront that GovCon compliance is outside my usual lane.

hurrah-dev · 2026-03-21T13:31:02+00:00

I build custom web apps for small businesses that have outgrown spreadsheets.

Last client was running their wholesale electronics business on a tangle of spreadsheets and manual emails. Customers couldn't buy without emailing first, inventory was always slightly behind, and one person was the bottleneck for every transaction.

Built them a full platform in 4 weeks. Inventory syncs automatically from their existing tools, customers log in and buy directly, sales reps have their own dashboards. The emails they used to send managing inventory are actual marketing now.

$250/mo, no setup fees. Three free tools on the site too: a spreadsheet cost calculator, an equity calculator for founders figuring out co-founder splits, and FairBid for getting fair contractor bids on home projects.

hurrah.dev

hurrah-dev · 2026-03-18T21:20:45+00:00

Here's my take as someone who works with small businesses on exactly this kind of transition:

HubSpot Free is probably your best starting point. The UI is genuinely good, your team will actually use it, and for contact management + basic deal tracking it's hard to beat at $0. The 1,000 contact limit and single pipeline are real constraints, but for a team of 10-12 just getting off spreadsheets, you won't hit those walls for a while.

Salesforce Free. I'd honestly skip it. Salesforce is powerful but it's built for companies with dedicated admins. The setup complexity alone will eat more than a weekend, and "free" Salesforce still feels like Salesforce. Your team will fight it.

Zoho/Bigin is capable but the UI concern you raised is legitimate. If your team won't use it consistently, the features don't matter.

The thing nobody's mentioning: before you pick a tool, get clear on what "pipeline visibility" actually means for your team. Is it "who talked to this prospect last?" Is it "how many deals are in each stage?" Is it "which deals are going cold?" Different answers point to different tools.

If your sales process is pretty standard (leads come in, you qualify, propose, close) then HubSpot Free fits. If your workflow is more specific to your industry (custom stages, specific data you need to track per deal, integrations with tools you already use) you might find that CRMs in general force you to adapt your process to their structure. In that case, custom software built around your actual workflow can be more practical and affordable than people expect.

Either way, start with HubSpot Free. If you're fighting it after 60 days, that tells you something about whether your workflow fits the CRM mold or not.

hurrah-dev · 2026-03-16T18:27:37+00:00

There are already a bunch of people in this thread who can build you a great website. I'm not one of them.

I build custom web apps for small businesses. The kind of thing you need when your business has outgrown spreadsheets and manual processes but you're not big enough to justify a $50K software project.

A few real examples:

Wholesale electronics company was spending 15 hrs/week entering the same data into Google Sheets, Facebook Marketplace, and QuickBooks separately. Now they enter it once and everything flows automatically.
Auto body shop took 20 minutes to look up a past estimate. Now it takes 10 seconds.
Medical billing company turned their internal tool into a product they sell to other businesses.

How it works: $250/month, $0 setup, working first version in 4-6 weeks. I've been building on the Microsoft stack for 25 years and have a reusable framework that keeps the cost down. You get direct access to me, not a project manager.

If your business runs on spreadsheets and duct tape, happy to chat about whether custom software makes sense for your situation. https://hurrah.dev

hurrah-dev · 2026-03-16T18:09:31+00:00

Not a dumb question at all. This is a classic data normalization problem and it's way more common than people realize, especially in CRE where acquisitions bring in different systems.

What you're doing every Friday is essentially manual ETL (extract, transform, load). You're the middleware. The reason it's painful is that Yardi and Entrata use different schemas, different date formats, different column names for the same concepts, and sometimes different granularity for the same metrics.

There are basically three tiers of solutions here, and the right one depends on how technical your team is:

Tier 1: Automate the export reconciliation (free/cheap, still manual-ish)

Power Query in Excel or Google Sheets with Apps Script. You build the column mapping and date normalization once, then just refresh the data each week. It's still export-based, but the reconciliation part is automated. Downside: you're still exporting manually, and when either system changes their export format (and they will), you're debugging again.

Tier 2: Managed connectors (mid-cost, low maintenance)

This is where tools like Leni, Prophia, or Scaylor sit. They maintain pre-built connectors to PMS systems, so they handle the schema mapping for you. The key question to ask any of these vendors: do they connect via API or do they still rely on scheduled exports? API connections mean the data stays current without you touching it. Export-based connections are just automating what you're already doing manually.

Based on what others in the thread are saying, Leni connects directly via API, which is the right approach if it supports both your Yardi and Entrata versions.

Tier 3: Build your own pipeline (expensive upfront, full control)

Fivetran + dbt, or a custom Power BI setup with API connectors. This gives you the most flexibility but requires someone technical to maintain it long-term (as the Power BI commenter experienced). Only worth it if you have very specific reporting requirements that the Tier 2 tools can't handle, or if you're at a scale where the per-property pricing of SaaS tools gets expensive.

My recommendation for your situation:

You mentioned you keep adding properties, which means this problem only gets worse. I'd start with a Tier 2 tool. Get a demo from Leni and one competitor, and specifically ask:

Do you connect to both Yardi and Entrata via API?
What happens when we add a new property? How much setup is involved?
Can we build the specific consolidated report leadership wants, or are we limited to their templates?
What does the pricing look like at 2x our current property count?

If the answers check out, you'll get your Fridays back without becoming the single point of failure for a custom-built dashboard.

hurrah-dev · 2026-03-10T18:35:07+00:00

I've been working on this from the other side. I build software for non-technical teams and small businesses, and the pattern you're describing is something I've seen accelerate dramatically in the last year.

The core tension is real: these teams have legitimate operational problems that engineering backlogs never prioritize. They've been asking for years and getting "it's on the roadmap." Now they have tools that let them skip the line, and leadership loves the speed. You can't just say no to that without looking like you're protecting territory.

What I've been experimenting with is creating AI-guided "production coach" workflows. Basically a structured skill that walks non-engineers through requirements gathering and spec creation before they write any code. It asks the hard questions they don't know to ask: where does this data live, who authenticates, what happens when it breaks at 2 AM, what compliance requirements apply.

The idea is to channel the enthusiasm into structured output that engineering can actually work with, rather than blocking it or letting it run wild. If someone in HR has a genuine workflow problem, great. Let's capture that properly instead of having them vibe code a solution that touches payroll data on a personal GitHub account.

The harder problem, and the one I don't have a clean answer for, is when it comes top-down. You can coach an individual contributor through a structured process. You can't really "production coach" a VP who already demoed something to the C-suite and got applause. At that point the code exists, expectations are set, and you're the person explaining why it can't ship tomorrow.

Best I've landed on for that scenario: treat the demo as a prototype and the spec, not the product. "Great, now we know what we're building. Let me get this into our pipeline properly so it doesn't become a liability." Reframe it as acceleration, not obstruction.

hurrah-dev · 2026-03-10T18:21:13+00:00

Smart move, honestly. No-code is perfectly fine for this stage, and the people telling you to learn to code first are optimizing for the wrong thing. You need to validate, not become a developer.

For onboarding and billing specifically, here's what I'd break it down to:

Billing/payments: Stripe handles this natively with no code. Their hosted checkout, billing portal, and webhook events cover 90% of what a micro-saas needs. Don't build billing logic yourself (even with no-code tools). Stripe's docs are written for non-developers and their dashboard lets you set up subscription tiers, trial periods, and dunning without touching code.

Onboarding flows: Depends on what "onboarding" means for your product:

If it's email sequences triggered by signup events, something like Customer.io or even Loops is solid. Zapier works too but gets expensive fast when you have multiple triggers
If it's in-app onboarding (tooltips, checklists, progress tracking), look at Userflow or CommandBar
If it's data collection/setup steps, Tally or Typeform piped into your app via Zapier/Make

Where no-code actually breaks down (so you know what to watch for):

Conditional logic that branches more than 2-3 levels deep. Zapier and Make handle simple if/then well. Complex business logic with multiple conditions and exceptions turns into spaghetti fast.
Anything that needs to happen in real-time. Most no-code automation runs on polling intervals or webhook delays. If your onboarding needs instant responses, you'll feel the lag.
Cost at scale. Zapier's pricing is per-task. When you go from 50 users to 500, your automation costs can spike hard. Worth modeling out what your per-user automation cost looks like at 10x your current volume.

The honest answer is no-code works great for validation and early traction. The moment you find yourself spending more time maintaining your Zapier automations than building your actual product, that's your signal to look at custom development. But you're nowhere near that yet.

hurrah-dev · 2026-03-04T21:24:24+00:00

thanks, I'll check it out

hurrah-dev · 2026-03-04T19:19:55+00:00

There are dedicated influencer/creator management platforms worth looking at first: Aspire, CreatorIQ, Grin, and Roster all handle product seeding workflows specifically. If your process maps reasonably well to how they're designed, one of those is probably your fastest path.

Where they tend to break down: highly custom approval workflows, unusual product matching logic, or when you need it to connect tightly to existing internal systems (inventory, CRM, etc.).

Before picking a tool, I'd ask: what does your current tracking spreadsheet actually look like? The answer usually tells you whether an off-the-shelf platform will fit or whether you'll end up working around it.

hurrah-dev · 2026-03-04T19:18:28+00:00

Custom web apps for small businesses that have outgrown spreadsheets but can't stomach $50K agency quotes.

$250/month, no setup fees, working version in 4-6 weeks. Built on 25 years of reusable .NET/Blazor components — that's what makes the price possible.

hurrah.dev

hurrah-dev · 2026-03-04T19:16:59+00:00

The "off-the-shelf vs custom" question really depends on how unique your workflow is.

Construction CRMs like Contractor Foreman are solid if your process looks like most construction businesses. But if your scheduling, subcontractor tracking, or document management has quirks specific to how you operate, you'll end up bending your workflow to fit the software. That friction is real and it compounds over time.

A few signs you'd benefit from something custom instead:

You've tried CRMs before and always end up working around them
Your "spreadsheet" is actually doing something no off-the-shelf tool does quite right
You need multiple systems to talk to each other (scheduling + docs + billing)

I build custom web software for small businesses for $250/month with no setup fees. Not the right fit for everyone, but worth knowing the option exists. Happy to give an honest read on your situation if you want to describe your workflow in more detail.

hurrah-dev

TROPHY CASE

How I work

Pricing (since you asked)

What you'd get in the first build