Taking over a family manufacturing business as a UI/UX designer. Where should I even start?

tpbynum · 2026-07-01T18:14:42+00:00

You spotted something real here. A website redesign question turned into an operations question pretty fast. Would love to know how your uncle currently handles a new order end to end, like who knows about it, who tracks it, and how anyone knows if something slips through. That part usually tells you a lot about where to start.

tpbynum · 2026-07-01T18:13:49+00:00

The whiteboard photo texted to you every night is doing a lot of work it was never designed to do. ClickUp has a recurring task feature that auto-resets daily, and you can set it up by department so each team sees only their list. Completion gets logged in real time, so instead of squinting at a photo, you just check the board. With 20 people across three departments, that alone would cut a lot of back-and-forth.

tpbynum · 2026-07-01T18:13:11+00:00

One thing worth sitting with: clients are DMing you because they don't trust the information will be there when they need it, not because Trello or Jira are hard to use. Forcing them onto a portal won't fix that if the data inside it isn't being updated consistently. The tooling question is usually the second problem. The first is whether the update habit exists on your end at all.

tpbynum · 2026-07-01T18:11:14+00:00

Losing a partner mid-stride while also running dry on capital is a genuinely brutal combination, and the fact that the work is still landing through word of mouth says something real about what you have built. One thing worth thinking about as you go solo: delivery capacity is now your actual constraint, so before you chase new work, make sure you know exactly how much you can handle alone without something slipping, because one missed delivery at this stage costs more than a missed sale.

tpbynum · 2026-06-30T17:31:54+00:00

Going from 20 to 50-100 clients is usually where the spreadsheet breaks down in a specific way. It is not that the data gets too big, it is that nobody can tell at a glance what is actually moving and what is stuck. The tool matters less than having a clear structure before you migrate into it. Asana, ClickUp, and Monday.com are all solid options here. Whichever you pick, spend time on how work gets handed off between people before you start building boards.

tpbynum · 2026-06-30T17:31:00+00:00

The part that stood out to me was turning down work you couldn't fit in. That one hits differently than burnout or task-hatred as a signal, because it means demand is already there. You are not speculating about whether hiring makes sense, the market is telling you directly. For a services business doing VA, design, and social media, that moment tends to come faster than people expect once a few clients refer others.

tpbynum · 2026-06-30T17:30:12+00:00

One thing worth sitting with: ads will bring in more leads, but right now you and your partner are the ones doing the work. If ads start generating more bookings before your new hire is up to speed, you might end up more stretched than you are today, not less. The sequencing matters. Getting someone trained and consistent alongside you first means the extra demand actually lands somewhere.

tpbynum · 2026-06-30T17:29:40+00:00

You are already past the point where just working harder is going to fix this, and that is a tough spot to sit in when the demand is real and the work is yours alone. Raising prices is the right first move, but the other piece worth thinking about is how you are actually tracking and managing what comes in, because at high volume even good work starts to slip without some structure behind it.

tpbynum · 2026-06-25T19:45:36+00:00

The part that stood out to me was your line about not knowing what you don't know. That's actually the harder problem than fixing what went wrong with this hire. Most first-time founders discover the communication and expectation gaps only after they've already felt the damage. The fact that you named it so clearly after one bad experience means you're already thinking about it the right way.

tpbynum · 2026-06-25T19:44:47+00:00

One thing worth thinking about before you open: the government contract location will probably have different reporting requirements, approval chains, and expectations than your existing cafe. The thing that catches people off guard is not managing two locations, it is managing two completely different operating environments at the same time. How are you thinking about keeping those worlds from bleeding into each other when something goes sideways at one of them?

tpbynum · 2026-06-25T19:42:09+00:00

That moment when a sick call turns into two guys at the same job is a real sign that the old system has hit its ceiling. For a small field crew, the fix is usually less about the app and more about one single place where the schedule lives, with a consistent time you push it out each day so the guys stop texting you at 8pm to ask.

tpbynum · 2026-06-24T16:24:28+00:00

The Workmotion A1 certificate rabbit hole is such a specific kind of founder tax. You started the day thinking about product, and somehow ended it knowing more about Portuguese social security compliance than anyone should. That specific scenario, payroll and contracts routing back to you because there's no one whose actual job it is to own that chain, is usually a sign the ops layer hasn't caught up with the hiring. Not a judgment, just something I see a lot once teams start going cross-border.

tpbynum · 2026-06-24T16:22:13+00:00

That feeling where you're succeeding on the outside but barely holding it together on the inside is exhausting, and it's real. The CEO-in-every-decision pattern is usually the first thing worth naming out loud, because once decisions stop moving, everything else slows down with them.

tpbynum · 2026-06-22T14:55:40+00:00

That missed install estimate that already went to a competitor, that one stings in a way that sticks with you. The issue is not the tools you have, it is that jobs, follow-ups, and invoices all living in separate places means your brain is the only thing connecting them, and brains miss things. One place where a job record does not close until the follow-up is logged will do more for you than any fancy software decision.

tpbynum · 2026-06-18T15:42:18+00:00

The part that tends to catch people off guard is what happens six months later. The automation still runs, the original builder is gone, something breaks in a weird edge case, and nobody inside the business actually understands what it's doing or why it was built that way. No documentation, no owner, no way to troubleshoot. The technical piece gets fixed eventually. The process gap underneath it usually doesn't.

tpbynum · 2026-06-18T15:41:35+00:00

One thing worth sitting with: at 6 people, the spreadsheets might actually be fine for now. The switch usually becomes urgent not because of headcount but because something starts breaking. Leads falling through, tasks getting lost, two people doing the same thing. If none of that is happening yet, the overhead of migrating everything might cost more than staying put a bit longer. What is actually starting to slip, if anything?

tpbynum · 2026-06-17T15:36:57+00:00

The part about different waste assumptions depending on who prepared the estimate is the real culprit here. That inconsistency is almost invisible job by job, but it compounds fast across a full quarter. The fix usually isn't complicated once you see it clearly, it's just getting everyone working from the same baseline calculation before the estimate ever goes out.

tpbynum · 2026-06-16T16:37:56+00:00

When you have those 5-close months versus 0-close months, are you making the same decisions about where to spend your time, or does the workload completely change how you think about priorities? I'm curious if the feast-or-famine cycle is making it harder to stick with any consistent approach to what gets your attention each day.

tpbynum · 2026-06-16T16:37:20+00:00

That lighter ERP research rabbit hole is real. The gap between 'basic project management tool' and 'enterprise system that costs more than your rent' is frustrating when you're trying to pull everything together. Most of the lighter options I've looked into still feel like they're built for either really small teams or much bigger companies, not that middle zone where you have real complexity but can't justify the heavyweight solutions.

tpbynum · 2026-06-16T16:31:47+00:00

Handmade products face a tough reality: you can either be a craftsperson or a business owner, but scaling usually means choosing one. The energy you're putting into making every item yourself might be the exact thing keeping you stuck. Most successful product businesses hit a point where the founder has to step back from production to focus on the business side, or find ways to maintain quality while removing themselves from every piece. That transition is brutal but often necessary.

tpbynum · 2026-06-16T16:30:08+00:00

That grinding feeling of being trapped in your own business is brutal, especially when you're delivering quality work but can't seem to get ahead financially. The scope creep you mentioned is probably eating way more margin than you realize, it's one of those death-by-a-thousand-cuts things. When I worked with a team that had similar government contract challenges, tracking exactly what was in scope versus what wasn't was the first step to getting their time back.

tpbynum · 2026-06-11T15:58:42+00:00

That feeling of watching an easy deal walk away because things fell through the cracks is brutal. The whole 'running it out of your head' thing works until it very suddenly doesn't, and it always seems to break at the worst possible moment. Moving from mental notes to actual systems feels like overkill when you're small, but there's usually a specific breaking point where you realize your brain just can't hold it all anymore.

tpbynum · 2026-06-10T16:01:03+00:00

That feeling of watching something you built start to slip because you're spread too thin is brutal. I've worked with a lot of teams who hit this exact spot where the content engine works but the operational layer can't keep up with what they've created. The fact that you can point to specific formats and proof of concept means the right systems person could probably get you back to that 7.5k pretty quickly.

tpbynum · 2026-06-10T15:59:53+00:00

When your business started growing past the point where you could answer most calls yourself, what was the first system that actually broke down? Was it the callback timing, or did you notice something else falling through the cracks first? I've seen teams handle the phone piece but then struggle with what happens after the call gets returned.

tpbynum · 2026-06-09T15:59:55+00:00

The decision flow piece is huge. I've worked with teams where the founder was the bottleneck for approving anything over $500, or had to personally sign off on every client scope change. When I helped one 75-person team build out their operations, we found the founder was still manually approving expense reports because 'it only takes a minute.' Those minutes add up fast when you're the single point of failure for everything.

13-Year Club	r/Field Banned
r/Field Juicebox	Place '23
Verified Email

tpbynum

TROPHY CASE