Scaling a Business: Challenges and Advice from First-Time Entrepreneurs

The challenge was that I was the product. I ran a photography and content business, and every dollar came out of my own hands. I raised my rate from $400 a shoot to $4,000 in under a year, which fixed my income but not the real problem. I still had to be in the room for anything to happen, so growing meant working more days, and there are only so many days.

What changed it was giving the work away. I hired cheap editors and handed them my own process written down, step by step. That took an account to 75,000 followers in 4 months without me touching a single edit. The same idea now runs on software instead of people. 150+ automated routines handle my content, my follow ups and most of my back office, and over 4,500 posts have gone out and been tracked that way.

My advice: before you hire anyone or buy any tool, write down exactly how you do the thing you are best at. Most founders stay stuck because that standard only lives in their head. Once it is on paper, a person or a machine can hold it, and your job becomes checking the output instead of doing the work.

The hardest part of scaling Pageloot wasn’t getting users, it was figuring out which users actually mattered.

Early on, we had signups from dozens of industries. Restaurants, real estate agents, event organizers, healthcare clinics. Everyone could use QR codes, so we tried to serve everyone. The product roadmap became a mess. Support tickets pulled in 10 directions. We were growing but not compounding.

The mistake was treating “any customer” as a signal of product-market fit. It isn’t. Wide adoption without a clear ICP just means you’ve built something generic. We had to deliberately narrow down, pick the verticals where we saw the strongest retention, and build features specifically for them. Marketing agencies turned out to be our biggest segment, and once we committed to that, everything got easier. Messaging, onboarding, feature priority.

The setback that forced the decision was a rough quarter where churn spiked. We dug into the data and found that the churned users were almost entirely from verticals we’d half-built for. We’d attracted them with broad promises but hadn’t delivered the depth they needed. Losing them was painful but clarifying.

The approach after that was simple: talk to the users who stayed and build for them. Not the loudest complainers, not the edge cases. The ones who renewed without prompting. We now have 20,000+ brands using Pageloot across 110 countries, and the growth that’s actually stuck came from going narrow first, not broad.

For anyone trying to scale, the advice is this. Pick one customer type and go deep before you go wide. Growth feels counterintuitive when you’re saying no to potential customers, but saying yes to everyone is how you build a product nobody loves. And watch your retention data closer than your acquisition numbers. New signups flatter you. Retention tells you the truth.

The hardest part of scaling wasn’t the build, it was capital. Jessica and I were trying to open a beer spa in the US—a category that didn’t exist here—with no comparable P&L for a bank to underwrite. Every traditional lender said no. What flipped it for us was reframing those rejections: instead of treating them as failure, we used the rejection letters as qualification documents for a Denver economic-development loan and a nonprofit SBA lender. The “no” from banks was literally the proof of novelty those programs required.

My advice for first-time founders: if you’re building something the market has no reference point for, stop pitching it to institutions built to fund reference points. Map the capital stack to the stage of your concept—municipal programs, CDFIs, and mission lenders exist specifically for what banks reject. And keep every rejection letter. We opened February 2021, mid-COVID, because we treated ours as assets, not scars.

The challenge that caught me out scaling EV Cable Hub was that growth ate cash faster than it made it, and as a first-time founder I had assumed more sales would simply mean more money in the bank. Instead, every jump in orders meant buying the next batch of stock before the last one’s takings had landed, and the faster we grew the tighter things felt.

It came to a head when one of our best-selling cables, a proven line I knew would sell, went out of stock for the best part of 3 weeks during a demand spike, because I could not fund a deep enough reorder in time. That was not a dud sitting on a shelf, it was the opposite, a winner I was losing sales on because the working capital was tied up elsewhere and the timing ran against me. Watching orders I had earned go unfilled was a harder lesson than any slow product.

The way I approached it was to frame cash, not demand, as the thing that governed how fast we could grow. I staggered reorders so I was not committing everything at once, kept a buffer rather than spending to the edge, and held enough cover only on the proven sellers while letting unproven lines earn their place first. Slower, steadier, and far less frightening.

My advice to anyone scaling for the first time is that growth is a cash problem before it is a demand problem. Selling more is the easy part. Financing the stock, and the gap before the money comes back, is what limits you, so protect your liquidity as fiercely as you chase your sales. A shop that grows a little slower but never runs dry on its winners beats one that sprints and stalls.

The single biggest challenge I faced scaling Prime wasn’t the work. I knew the work. I’d been in the trades since 1998. I knew how to run a job, how to price it, how to deliver it right. What I didn’t fully see coming was how hard it would be to find and keep the people who could do the same work at the same standard without me standing over every job.

Finding and retaining talent has been the most difficult thing we’ve faced since 2012. I’ll say that plainly and without dressing it up. It’s an industry-wide problem, but that doesn’t make it easier to manage inside your own company. The business can grow. The revenue targets can climb. But if you don’t have the right people to actually deliver the work, none of those numbers mean anything.

The way I approached scaling was to build systems before I needed them. Not after the pain point hit. ServiceTitan gave us the operational structure to handle more jobs without everything running through me personally. Automated communication, dispatch optimization, post-job follow-up, all of it running consistently whether I was on a job or not. That’s what allows a company to scale without the quality degrading.

The other thing I learned is that scaling and growth are not the same thing. Revenue can go up while the business gets harder to run. Real scaling means the business performs better as it gets bigger, not just bigger for the sake of it. Every hire, every system, every process has to make the customer experience more consistent, not less.

The advice I’d give any first-time entrepreneur looking to grow is this: don’t wait to build the infrastructure until you feel like you need it. You’ll always feel like you need it too late. Build the systems, build the standard, hire slowly and carefully, and never let the growth outrun your ability to deliver on the promise you’ve made to your customers. The reputation you build on the way up is the thing that determines how far up you actually get.

When we started scaling AGO, one of the most unexpected challenges I faced as a co-founder was getting our growing engineering team aligned on a new way of working without slowing down our momentum. We were transitioning our product architecture from basic chatbots to stateful AI agents. This meant our developers suddenly had to get comfortable with non-deterministic testing, which requires a completely different mindset than traditional software testing.

We quickly realized that standard training seminars and separate learning portals weren’t working. The lessons were too disconnected from the code, and pulling engineers out of their workflow was hindering our growth. To actually scale our output, we had to change how the team learned on the job.

We approached this by embedding a feedback loop directly into their daily deployment process. We built an automated pipeline where a separate language model acts as a judge. Now, whenever an engineer tests a new update, this judge runs simulated customer conversations against a behavioral rubric. If a code change causes an agent to hallucinate a policy, the developer gets a short, specific explanation right in their terminal, tied to the exact lines they just wrote.

For others looking to scale a technical team, I usually suggest bringing the feedback loop as close to the actual work as possible. Within a few weeks of moving these micro-lessons into the terminal, we noticed our developers proactively adjusting their approaches before the automated judge even flagged an issue. Scaling a product isn’t just about hiring or upgrading infrastructure; it often comes down to how efficiently your team can internalize new concepts without having to step out of their core workflow.

One of the biggest challenges was scaling a business in a category that many people did not fully understand yet. When I started Zeva Hair Spa, scalp care was not discussed in the same way as skincare or wellness. Hair loss was often something people felt embarrassed about, so part of growing the business was not simply attracting more clients; it was helping people feel comfortable seeking support in the first place.

I approached this by focusing on education rather than pushing treatments. We explain what is happening on the scalp, why a particular treatment is recommended, and just as importantly, when an advanced treatment may not be necessary. My own journey began after experiencing hair loss following cancer treatment, so it was important to me that clients never felt pressured or judged. As we grew, I continued investing in trichology knowledge, new research, and people who could combine technical expertise with genuine care.

My advice is not to assume that growth only means selling more or opening more locations. Sometimes you first have to build trust in the category itself. Be clear about the problem you are solving, explain your work in a way clients can understand, and do not dilute what made people believe in you at the beginning. Once that trust is there, growth becomes much more sustainable.

My challenge was that the thing clients hired us for was the first thing growth would have destroyed.

People come to us because changes go live in hours. That only works because the person designing the page is also the person building it and the person the client speaks to. Every standard way of scaling an agency, adding project managers, adding juniors, adding layers of process, puts distance between those roles and slows everything down.

So I scaled depth instead of headcount. We stayed at five people and moved most clients onto retainers, which means around eighty percent of our revenue now comes from teams we already know, with no re-onboarding and no new statement of work for every page. Same team, more output, no dilution.

My advice is to get specific about what you are actually selling before you grow. If your advantage is speed or taste, adding people is often subtraction. Growth should first look like doing more for fewer clients, not more clients.

Our biggest scaling problem was one nobody warns you about: half the year our customers are unreachable.

We sell to marinas, and a harbourmaster in July is not taking a discovery call. The boats are in, the phone is ringing, and software is the last thing on their mind. For our first stretch we ran the company like a normal SaaS business with even monthly targets, and we kept missing them in summer and blaming ourselves.

What fixed it was accepting the rhythm instead of fighting it. We now build the year around two seasons. Winter is for selling, onboarding and migrating data, because that is when operators have time to sit down with us. Summer is for support, watching the product get used under pressure, and collecting the feedback that shapes the next release.

The advice I would give is to find out what rhythm your customers already live in before you set your growth plan. Forcing your calendar onto theirs mostly just makes your team feel like it is failing.

In our particular situation, we weren’t competing against other startups. We were competing against firms that had been building trust for years before we opened our doors.

Regulatory technology for medical device manufacturers is not a young industry. The firms we compete against built their reputations and client relationships over many years. As a first-time entrepreneur, the obvious approach would have been to try to match their scale directly, more staff, more offices, more of everything they already had. That’s a losing game against companies with that much of a head start.

What actually worked was building AI directly into our regulatory workflow from the beginning, something far easier to do as a new company than as an established one carrying years of legacy process. That gave us lower costs and faster delivery than firms still running everything manually. Don’t try to out-resource entrenched competitors. Build something structurally different that they can’t easily retrofit into how they already operate. Being new was the advantage, not the obstacle.

One of the biggest challenges I faced as a first-time entrepreneur was learning that growth does not always mean serving more clients. Sometimes, a business can become more profitable by providing fewer services at a higher level.

In the early stages of my photography business, I priced my services below the local market average. I believed that lower prices would help me attract more clients and generate more consistent cash flow. However, I soon realised that this approach does not always work for a local service-based business. There is a natural limit to how many clients one person can serve, especially when every service requires a significant amount of time, care, and personal attention.

Instead of continually trying to increase my client volume, I began focusing on increasing the value and profitability of each service I provided. I invested more in the quality of my work, the client experience, and the systems behind the business. My goal shifted from quantity to quality.

The most difficult part was training myself to accept that being busier does not necessarily mean the business is healthier or more profitable. Slower periods do not automatically mean I am failing. When prices increase, it is natural for the number of clients to decrease, but that does not mean revenue or profit will decrease with it.

My best advice is to separate your emotional reactions from your business decisions. This is especially important when you still work directly with clients, because an empty calendar can feel much more alarming than it actually is. Look at revenue, profit margins, workload, conversion rates, and client value. Let the numbers guide your decisions rather than choosing whatever feels most comfortable in the moment.

You can’t scale complexity. My first 3 times I started a business I made a “perfect” process that would do everything I wanted, but the problem was it was complex. I started a company that made surf and boogie board kiosks for people to rent at the beach. It was a machine that they could just tap their card, get the board, and go play, then return it to the kiosk when they are done. It was a great idea. To make the kiosk, we found the best software, applied it to the best material to make it waterproof, found the best locks, got the best graphics applied, used special grommets, and did all of this thinking we would buy in bulk to make it cheaper since we were a startup and money was tight. What ended up happening was we had supplies from 10 different places, processes that happened in 3 places, and huge list of partners that we relied on. It was complex. It created the best tool, but because it was complex it had multiple fail points. Just 1 supplier could derail our process, and we had lots of points that could break.

When you are trying to scale, not just grow, but scale to 10x or more what you are doing, then the complexity just gets in the way. The best thing to do when you are wanting to scale is to cut the unnecessary things and really focus on what the purpose of your business is. Know who you help and the problem you help them solve. Then focus only on solving that in the best but most simple way possible. That allows you to scale easily without all the fail points.

“The biggest lesson scaling my Disney hotel review business: content quality and distribution are two separate problems, and I originally treated them as one. I built something genuinely differentiated — firsthand data from 48 real hotel stays, things like real WiFi speeds and parking costs nobody else publishes — and assumed the content would find its audience on its own. It took real, deliberate work in SEO and structured content to convert that into visibility; one of my hotel comparison pages now ranks above Reddit and TripAdvisor for its exact search term. My advice to first-time founders: don’t confuse having a great product with having a plan to get it in front of people. Build both from day one.”

— Mark Patterson, Founder, DDadBudget.com

The scaling problem that caught me off guard wasn’t a lack of demand. It was the opposite. We built our first version of Pledge It to solve a fundraising gap we’d lived first-hand, and once we opened it up, close to a thousand athletes wanted in almost overnight.

We’d built it for internal use, and every workflow we’d shortcut for ourselves suddenly needed to hold up under real pressure. It’s a common trap for first-time founders. A product feels solid when you’re the only user, and it breaks in small ways the moment strangers start relying on it.

The same test came later, when Pledge It expanded to non-profits running their own campaigns beyond athletes alone. Each new organization exposed a workflow we hadn’t considered, from donor management to event logistics. Fixing those gaps before pushing growth further kept the platform from outrunning what we could support.

My advice to a first-time founder is to treat rapid interest as a diagnostic signal worth investigating rather than a milestone to celebrate. Growth will always find the parts of your product you haven’t tested yet. The founders who scale well go looking for those gaps before their customers find them.

One of the biggest challenges I faced as a first-time entrepreneur was realizing that revenue growth did not automatically mean we were ready to scale. In our business, there can be real gaps between when traffic runs, when advertisers pay, and when partner payouts are due, so timing and predictability mattered as much as dollars coming in. I approached scaling by tightening our cash flow planning and choosing more intentional growth, making sure we could honor every commitment before taking the next step. My advice is to look beyond top-line revenue and map the timing of every inflow and outflow so you can scale without putting pressure on partner relationships. When you manage cash flow with discipline, you build trust and create a stable foundation for long-term growth.

When I started Spendbase in 2022 as a first-time founder, my biggest challenge was equating growth with headcount. Every time we hit an operational bottleneck, I just threw a new hire at it. It’s a rookie mistake that absolutely torches your cash runway.

We’re at 180 employees now, but my approach to scaling completely changed. Our entire fintech platform is built on automating cloud and software cost-cutting for our clients.

I finally realized I had to apply that exact same ruthless efficiency internally.

My advice to first-time founders is to stop throwing payroll at broken processes.

If you hit a scaling wall, force your team to automate the workflow first. Only hire when the software literally can’t do the job.

One of the obstacles I encountered was automating the processing of customer orders. This required me to complete vendor invoicing and enter tracking numbers before I uploaded the order status to my system. Since I had another job, I had to do this spreadsheet work at night. I recorded all the steps of the process to automate the tasks, and the steps that I determined to be repetitive, I moved to scripts and scheduled tasks. I would advise someone to do a task to completion until edge cases, where the task would break, show up. The time I spent on manual processing helped me determine which orders would break the process.

The biggest hurdle when we first started out was just getting people to trust a brand new business. In the corporate world, buyers are incredibly risk-averse, so winning those first few accounts as an unproven vendor was tough.

We didn’t have a massive ad budget, so we literally just leaned on our friends and personal networks to get things going. We shared our merchandise with them, they talked about it with their friends, and it kind of snowballed from there. Hearing that positive user feedback early on is really what kept me motivated to keep pushing.

So we realised we had to stand out to keep growing. Instead of just selling generic products like everyone else, we pivoted to offering completely customised solutions. We focused on tailored packaging and curated gift sets for different occasions, which helped us build actual relationships instead of just doing one-off transactions.

Here is some of the advice that I would give to other businesses that are trying to grow their business:

Give your clients an end-to-end service. If you focus on understanding their actual needs from start to finish, you set yourself apart from generic suppliers.

Second, take charge of your production. You need to know exactly where your products are coming from and have in-house capabilities so you can actually guarantee the quality and delivery times.

And finally, look after your own team. Give them personalised gifts for their milestones and work anniversaries so you can retain your best people.

A real challenge in scaling was learning that brand and operations cannot grow on separate timelines. As a first time entrepreneur, I saw how quickly performance can flatten when the promise is strong but the experience feels uneven. I approached scaling by aligning the commercial strategy with the customer journey, so the expectations created upfront were matched all the way through. That alignment improved not only conversion, but also loyalty and word of mouth.

My advice is to treat growth as a full business discipline, not just a sales target. I found that the most scalable businesses are the ones that create trust repeatedly, not the ones that simply attract attention fastest.

One of the biggest challenges James Martucci, CEO of SideKix, faced as a first-time entrepreneur was not being able to find support. His first business was selling candy on the school bus. When he got caught, he was threatened with suspension. No one stopped to ask why he started the business or how they could help. No one said, “That’s entrepreneurial. Let’s figure this out together.” They simply told him to stop.

So he did.

But he didn’t stop being an entrepreneur. He just started another business.

That experience taught him one of the most important lessons of his life: not everyone will understand your vision, and that’s okay. Don’t let someone else’s limits become your own. Believe in yourself, keep building, and find people who believe in you too.

They’re out there.

In fact, that’s one of the reasons he created SideKix. Every entrepreneur deserves someone who says, “How can I help?” instead of, “You can’t do that.”

When James thinks about scaling, he doesn’t believe growth is just about showing numbers, chasing results, or reaching a certain financial milestone. Numbers matter, but they are only one piece of the story. They can be manipulated, adjusted, inflated, or represent only a single moment in time. They don’t always tell you whether you are actually creating something meaningful.

True growth requires looking deeper. Are you creating impact? Are you staying true to your mission? Are you building the right culture? Are you making decisions that create long-term value instead of short-term wins?

His approach to scaling has been focused on building a strong foundation and creating systems that help guide better decisions. That means balancing metrics with other important filters: the impact we are creating, the people we are serving, the culture we are building, and the long-term consequences of the choices we make today.

His advice to other entrepreneurs is to not let a number define your success. Use data to understand your business, but don’t let it replace your purpose. The goal isn’t just to grow bigger—the goal is to grow better. Build something that creates real value, stays aligned with your mission, and makes a lasting difference for the people you serve.

The biggest challenge I faced scaling our ORM work was learning that hiring operators beats hiring specialists every single time.

Early on, I made the mistake most first-time founders make. I needed automation built, so I hired developers. I needed content production at volume, so I hired writers. I needed client onboarding systems, so I hired project managers. Each hire was a specialist, and each one created a silo.

What broke first was response time. A client would ask for negative content suppression, then ask about review management, then need press release distribution. Three separate people. Three handoffs. The client experience was fragmented, and internal communication became the bottleneck. We were spending more time coordinating than delivering.

I noticed something odd during one hiring round. We needed someone to manage our n8n automation pipelines. I interviewed developers who understood code but had never touched a client. Then I interviewed an ops person who had run client operations at another agency and was willing to learn n8n from scratch. I hired the ops person. Within two weeks, she was building workflows the developers would have taken a month to scope.

That changed how we hire. Now I look for people who understand the client problem first and are willing to learn the tools second. Ops people who learn automation consistently outperform developers hired for automation roles, because they start from what the client actually needs, not what the tool can technically do.

The other thing that worked was making delivery overlap intentional. Instead of separating reputation, PR, and content into different teams, we started running one person across multiple functions for each client. The person handling reputation suppression also writes the client’s press releases and manages their media placements. It sounds like more work per person, but it actually moves faster because there are no handoffs. The client gets one point of contact who knows the full picture.

My advice: hire for adaptability, not expertise. People who have done one thing for ten years will keep doing that one thing. People who have done three things for three years each will figure out the fourth thing faster than you expect. Overlap beats specialization when you are still figuring out what the business actually is.

Early delegation of the operational flow is the primary issue which resolves the scaling up of a business as a first time entrepreneur.

When the business is in its early stages, the would-be business founders often attempt to personally be involved in all their communications with the clients. The speed of occurrence of operational bottlenecks is high. Docu-SOPs are key in facilitating a transition to real leadership as it enables remote employees to execute deliverables without any in-house supervision from the founder. It’s important to note that, in fact, it can save 20 hours of management time each week if you spend $1,000 per week on custom training templates. Standardized Handoffs reduce service errors by 35% during rapid expansion. So, delegation of daily tasks forms strong companies that can grow and expand effortlessly within the worldwide markets.

With outcome performance measures, leaders can be effective in dealing with teams remote from their home office as they build their business. This can get messy to deal with out-of-town teams when there’s no clear way to track their output. Clear metrics address this need. This allows leadership to have clarity on what explicit deliverables are happening and it doesn’t require them to constantly micromanage. Tracking dashboards, which are easy to use, reduce weekly meetings from 60 to 5 hours. Groups that have unambiguous objectives, attain their goals consistently 90 percent of the time. In most cases, objective measures are able to eliminate ambiguity and shine a light on the operational inefficiencies in just three business days.

Setting up consistent means of acquiring clients gives new business owners consistent revenue growth. Variable and unpredictable cash cycles result from alternative referral systems. A lack of cash flow will destroy momentum. Setting up outbound workflows is a task that can be done with a clear idea of how many conversions you are likely to get. This was what they did. They started creating outbound workflows with predictable conversions and this changed sales outreach into a mathematical game. As you might imagine though, a $5,000 per month investment in organized marketing campaigns results in 15 suitable sales meetings each month. By improving the documented process of onboarding, 25 percent more customers stay for six months after being onboarded. Sustainable expansion occurs when there are predictable weekly acquisitions that are sustained.

My first scaling problem was that clients had hired me personally, and the contract said otherwise.

For the early years, every relationship ran through me. I took the first call and I made the follow-up. That works beautifully at a certain size, and it is a trap. Referrals came from people who trusted me by name, so each new client arrived expecting the founder. Growth meant more of those expectations, and there was one of me. I kept solving it by working longer hours, which is the most expensive answer available to a founder.

The instinct is to fix this with process. Write the playbook and hand it off. We did that, and it helped with the mechanical work. It did nothing for the part that mattered. What clients were buying was judgment, the read on a situation that tells you which defensible option is the right one this week. You cannot document judgment. You can only transfer it.

So we changed how we grew. I stopped delegating tasks and started sharing rooms. Colleagues joined difficult client conversations long before they were ready to lead them, and afterward I walked them through my reasoning, including the calls I got wrong. Hiring shifted toward character and judgment ahead of credentials, because judgment travels with a person into situations no playbook anticipated. We also accepted a slower pace. I declined work that would have put someone in front of a client before they had earned that seat.

My advice is to decide early what you refuse to scale. Every book tells you to find the bottleneck and remove it. Some bottlenecks are the reason the business works, and removing them removes the business. Name the standard you will not lower, then grow only as fast as you can staff it honestly.

A company built on relationships grows at the speed of trust, and that speed runs slower than any spreadsheet would like.

My biggest challenge is addressing the needs of the client. In my local community, there is a lack of business, new business, or economy (smaller town). My concentration when I started was business, business, business. Now, I have changed a bit, concentrating on individuals in my local town and business in my bigger towns.

One major challenge I faced was letting client work consume all my time so the business itself did not get the attention it needed to scale. I addressed that by creating a regular “Power Hour”—a protected block of time dedicated solely to strategic, long-term work. That practice made clear that our business deserved uninterrupted attention and forced us to build systems instead of only responding to immediate client needs. My advice to other founders is to schedule and protect that time as sacred, use it for high-leverage tasks, and defend it from interruptions so growth work actually gets done.

Honestly, the hardest thing wasn’t the tech. We spent years on the execution engine before launching. That was the easy part because it was within our control.

The real challenge was trust.

When you’re a first-time founder with no brand, no track record, and you’re asking people to deposit their BTC into your platform—why would anyone say yes? Banks have FDIC insurance and marble lobbies. We had a GitHub repo and a whitepaper.

How we approached it: We didn’t try to out-market established players. We went the opposite direction: radical transparency.

Instead of saying “trust us,” we said “don’t trust us—verify these four things yourself”:

1. Here’s our LEI registration on GLEIF—look it up.

2. Here’s our ISO 27001 and ISO 20000 certifications—check the IAF database.

3. Here’s exactly how the arbitrage engine works—read the technical paper.

4. Here’s our circuit breaker logic: it’s deterministic; no human override exists.

We also made a counterintuitive decision early on: don’t optimize for growth. Optimize for no incidents.

In crypto, one hack erases everything. So we spent the first three months post-launch with deliberately conservative risk limits. We turned away volume we could have captured. We let competitors grow faster. But when those six months passed with zero security incidents, zero downtime, and zero missed withdrawals, that became our moat. Users who deposited $1,000 came back with $30,000.

Advice for others trying to scale:

– Your first 100 users matter more than your first 10,000. Those early adopters either become evangelists or warning stories. Make sure they win.

– Ship the thing that can’t fail before you ship the thing that looks good. Nobody cares about your UI if they lose money.

– In trust-based industries, speed of growth is inversely correlated with duration of survival. Go slower than you think you should. The tortoise actually wins when people’s life savings are involved.

One practical thing that worked: we published monthly transparency reports before anyone asked for them. TVL, number of users, total yield distributed, security incidents (always zero). When you voluntarily disclose what others hide, people notice.