Build Less, Learn Sooner: How Presta Scopes an MVP

Vladeta Radovanovic started Presta in Belgrade in the winter of 2014. Twelve years on, the agency builds web apps, Shopify stores and AI automation, mostly for startups and companies that are growing fast. Its past clients include UNESCO and Audi, and the About page still describes the goal he started with: products that make a lasting difference for the business using them.

Not every founder who contacts Presta gets a build right away. If the idea isn’t clear yet, they’re usually pointed to a paid Discovery Workshop first. It takes one to two weeks and ends with a written scope and a fixed price. One of their MVPs, Trinigence, shipped three months earlier than planned.

Presta has been on NoRobots once before, in a piece about keeping clients for the long run. This time we wanted to talk about MVPs: what makes the cut for a first release, how to tell a founder isn’t ready to build, and what happens when you strip a product back.

How to choose MVP features for the first release

Presta often helps startups turn an idea into an MVP. How do you decide which features are essential for the first release and which ones should wait?

We start with one question: what is the single thing a user must be able to do for this product to prove its point? Not the vision, not the pitch deck version, just the one action that tells you whether people care. Everything that directly supports that action goes into the first release. Everything else goes on a list we call “after we learn something.”

In practice, founders come to us with 30 or 40 features, and most of them are reasonable. The problem is that every feature you add before launch is a guess, and every guess delays the moment you get real feedback. So we sort features into three buckets: things the core flow can’t work without, things that make the product feel trustworthy (login, payments, basic security, a clean onboarding), and things that are nice but based on assumptions about how people will use it. The first two buckets ship. The third waits.

A simple test we use: if a feature only makes sense once you have 1,000 users, it doesn’t belong in a product that has zero. Admin dashboards, advanced analytics, referral programs, multi-language support, complex permission systems: all of these are real needs eventually, but almost never on day one.

We also push founders to think about what can be done manually at first. If an AI recommendation engine can be replaced by the founder personally sending recommendations to the first 50 users, that’s weeks of development saved and a lot of learning gained. You automate once you know what’s actually worth automating.

When a founder isn’t ready to build yet

How can you tell when a founder needs a product built, and when they actually need more customer validation or a clearer strategy first?

Honestly, it usually becomes clear in the first conversation. If I ask, “Who is your customer?” and the answer is “everyone,” or I ask, “How will you reach your first 100 users?” and there’s a long pause, that founder doesn’t need developers yet. They need clarity.

There are a few signals we look for. Have they talked to potential customers, not friends and family, but people who would actually pay? Do they know what those people use today to solve the problem, and why it’s not good enough? Can they describe their go-to-market in a few sentences? If the answers are vague, building the product will just turn a cheap mistake into an expensive one.

This has become even more important with AI. Today, almost anyone can build an MVP in a few weeks, so building is no longer the hard part or the competitive advantage. Distribution, positioning and understanding the customer are. I’d rather tell a founder “don’t hire us yet” than take a 50,000 EUR project that will need a full pivot three months after launch.

When things are unclear but promising, we suggest a Discovery Workshop instead of a full build. It’s a short, paid phase where we map the users, the core problem, the riskiest assumptions and the smallest version worth building. Sometimes the output is a lean scope and a fixed price. Sometimes it’s a clickable prototype to show to customers before writing any code. And sometimes the honest conclusion is that the idea needs more validation, and that’s a good outcome too, because it saved the founder months and money.

How cutting features made a better product

Can you share an example where removing a feature or simplifying an idea led to a better product?

One that comes to mind is a startup that came to us wanting to build a two-sided marketplace connecting service providers with customers. The original scope had everything: a customer app, a provider app, in-app chat, booking with calendar sync, payments with split payouts, ratings, a loyalty program and an admin panel. On paper it made sense. In reality it was about six months of work before a single real booking could happen.

During discovery, we asked which side of the marketplace was harder to get. The answer was clearly the providers, and the founder already had personal relationships with about 20 of them. So we flipped the approach. Instead of two apps, we built a simple web booking flow for customers and gave providers a lightweight dashboard. No chat (phone and email worked fine), no loyalty program, no split payouts at first; the founder handled payments manually for the first few weeks.

The first version went live in roughly six weeks instead of six months. And because real bookings started early, the founder learned things no spec could have told us: customers cared much more about seeing availability instantly than about ratings, and providers wanted reminders far more than they wanted a fancy calendar. The features we eventually added were the ones users actually asked for, and a few of the ones we cut never came back because nobody missed them.

That’s the part founders often find surprising. Cutting features doesn’t make the product weaker. It makes it sharper, because every remaining feature has to earn its place.

Final Thoughts

Vladeta keeps it practical. Work out the one thing that proves the idea, ship only what supports it, and do the rest by hand until you know it’s worth building. He’s also happy to tell a founder not to hire Presta yet, which is probably part of why the agency is still around after twelve years. The marketplace story makes the point better than anything else in the interview: live in six weeks instead of six months, with the later features coming from real users and not from a spec.

Explore More Agencies

If you’re an agency, designer, or startup looking to boost your visibility, you can join NoRobots and become part of our curated network of trusted businesses. If you’re a brand or client searching for the right partner, our platform helps you discover agencies, designers, and startups you can rely on. Browse the listings and find the right fit for your next project!

Hiring for Judgment, Not Polish: Mattia Apostoli, Digital Project Manager

Mattia Apostoli works out of Vestone, a small town in Valle Sabbia, near Brescia. He calls himself a digital project manager, and a lot of his clients are the kind of businesses you’d expect around there: cheesemakers, a dentist, a carpentry shop, family hotels on Lake Garda. A few are bigger. One runs ferries to the Isle of Elba. Another makes design door handles. He’s been at this for about 14 years, and his site lists 57 websites he built himself.

He isn’t a one-man shop. He has a group of developers, designers and other specialists he brings in depending on the job. What doesn’t change is that the client talks to him. He sets the plan, hands the work to the right person, and answers for it if something goes wrong. That idea kept coming back in his answers.

The ferry company is Blu Navy, which sails from Piombino to Elba. Mattia worked with them from 2023 to 2025. Before he touched the website, he sorted out their email, phone system and servers, and he says telling the owner that had to come first was the hardest part. Then came the new site, two ticket kiosks at the port and an AI assistant. Visits to the site went from roughly 20,000 a month to over 100,000.

We first invited Mattia onto our podcast. He asked to answer in writing instead, since he’s more at home in Italian than in spoken English, so this one came together over email. We asked him about hiring without resumes, how he tests new people, and how he spots AI being used as cover for weak work.

How to identify talent without resumes

If you could build your dream team without looking at resumes or degrees, how would you identify the right talent?

A resume tells you where someone has been. I care about how they work, and the only way to see that is a real project together. That’s how my network of collaborators was built.

What I look for comes down to four things.

First, can they explain their work to a non-technical owner? Half of this job is translation. A brilliant developer who can’t tell a business owner why a choice matters is only half a professional. The people I keep can explain to the company what the technician needs, and to the technician what the company needs.

Second, will they say “you don’t need this”? I want people who would rather lose a sale than sell smoke. If someone never pushes back, I can’t trust their yes.

Third, do they bring bad news first? Mistakes happen. Hiding them is the problem. Once the strategy is set, my collaborators work on their own, so I need to hear about a problem from them, early, and know that nobody will ever go over my head with a client.

And they never stop studying. In this field, what you knew two years ago is already half outdated. A degree certifies the past. I’m more interested in what someone learned last month.

Sometimes the best talent is already inside the company, just in the wrong role. At Blu Navy, a ferry company sailing to the Isle of Elba, Gigi was a ground supervisor at the port. No resume would have called him a content creator. Once he had the space, his videos passed one million views.

My test is simple: a small, real job together. One week of work tells you more than any interview.

How the paid one-week test project works

You mentioned that a one-week project can tell you more than an interview. How do you structure that project, and what advice would you give another agency founder who wants to use the same approach?

The rule is simple: it has to be real work. No made-up exercise, no “redesign our logo for free.” I take a small, self-contained piece of a live project, something I would have to deliver anyway: a section of a site audit, a landing page, a set of product pages to rewrite, a small automation. And I pay for it.

I split the week into four parts.

On day one, I give the brief the way a client would give it to me: who the business is, what they want, what they can’t afford to break. Not a task list. The first thing I watch is the questions. Good people ask about the business before they ask about the tools.

Midweek, we have a short call, about twenty minutes. They explain where they are as if I were the business owner, no jargon allowed. That’s where I see if they can translate.

Somewhere along the way, there’s the thing that isn’t worth doing. Real briefs always have one. I don’t hide traps; I just watch whether they notice and have the courage to say so.

At the end of the week, they deliver three things: what they did, what they’d do next, and what went wrong. The last one matters most. If nothing went wrong, either they didn’t push hard enough or they aren’t telling me.

AI is allowed, of course. I use it on every project. I just want to know where they used it and what they checked by hand. Today, output is cheap. Judgment isn’t.

If another founder wants to try this, here’s what I’d tell them.

Pay for the test. Unpaid tests attract the wrong people and give you fake signals. Keep it small and real, too: one week, a real deliverable, low risk for the client. Never throw a new person straight at your most important account.

Judge the process, not just the result. A nice deliverable tells you little. How they asked, explained and flagged problems tells you how the next two years will go.

Stay the point of contact. The client shouldn’t feel like part of an experiment. You carry the responsibility; they carry the work.

And decide fast, with a reason. Yes or no, a clear reason respects their time, and it’s what makes good people want to work with you later.

How to spot AI used to hide weak thinking

As AI makes polished work faster to produce, what separates someone who uses it well from someone who is using it to hide weak thinking? Can you share a moment when that difference became obvious on a real project?

Polish used to be a signal of effort. It isn’t anymore. Today, anyone can hand you a clean, well-formatted, confident document in ten minutes. So I stopped looking at how the work looks and started looking at three other things.

The first is whether they can defend every choice without reopening the chat. I ask, “Why this and not that?” Someone who used AI well answers with the client’s business, their numbers, their constraints. Someone hiding behind it gives you generic best practices, or worse, “that’s what came out.”

The second is whether the work is about this client or could be about anyone. Weak work is interchangeable. Swap the company name and it still reads fine. Good work has fingerprints: the client’s real data, the words their customers actually use, the thing they can’t afford to break.

The third is whether they actually chose. AI makes it free to produce more pages, more ideas, more recommendations. When I deliver an audit, the client gets a list of priorities and one hour with me to decide the order. Sometimes the honest answer is “leave it as it is and fix two things.” An audit with forty priorities has none. Volume is the easiest way to hide that nobody made a decision.

Two projects show the difference better than any theory.

The first is Azzurra, the AI assistant we built for Blu Navy. The quick route was a chatbot fed with the FAQ page. It would have looked great in a demo and been useless at the ticket counter, because passengers don’t ask generic questions. They ask things like “Is there still room for my car on the evening ferry?” So the real work wasn’t the chat window. It was connecting Azzurra to the booking system, so she answers with real data. Today, she handles thousands of conversations.

The second is Dnd Magic, the private B2B area of Dnd Handles, an Italian manufacturer of design door handles. The easy version of a client portal is a login and a folder of PDFs. Magic is fully custom, designed around how architects and showrooms actually work: a library of 3D models ready to drop into their projects, a configurator where they can upload a photo of their own space to test finishes, price lists generated automatically for each client with their own discounts, in six languages, and AI built in where it really saves them time. Every feature is there because it answers a real need of Dnd’s clients, not because a tool made it easy to add.

In both cases, the same technology anyone can buy, completely different thinking behind it.

The short version: AI should make your thinking faster, not replace it. If you can’t explain the work without the tool open, it isn’t your work yet.

Final Thoughts

Most of what Mattia told us comes back to one point. Polished work doesn’t prove much anymore, so he pays attention to how people think. New collaborators get a real, paid week. The client conversation stays with him. And he would rather hear that a task isn’t worth doing than see it finished anyway. Azzurra and the Dnd portal show where that leads: the same tools anyone can buy, pointed at the one problem that actually needed solving.

Explore More Agencies

If you’re an agency, designer, or startup looking to boost your visibility, you can join NoRobots and become part of our curated network of trusted businesses. If you’re a brand or client searching for the right partner, our platform helps you discover agencies, designers, and startups you can rely on. Browse the listings and find the right fit for your next project!

How 3 Brothers Built an Inc. 5000 Agency — Josh Webber, Big Red Jelly

How do you grow a marketing agency past the feast-or-famine stage — and keep it growing for almost a decade? Josh Webber has an unusual answer: do it with your brothers. He co-founded Big Red Jelly in 2017 after selling his first company, and has since built it into an Inc. 5000 agency with 33 in-house employees. On the NoRobots Podcast, Vlad — co-founder of NoRobots and Digital Octane — sits down with Josh to unpack the decisions behind that growth: pricing, hiring, AI, and the clients he now turns away. Watch the full conversation above, or read the highlights below.

Working with family: swim lanes and “professional mode”

Running an agency with two brothers sounds like a recipe for conflict, and Josh doesn’t sugarcoat it: “there’s probably more cons than pros.” What fixed the early bumps was treating the company like a company — clear areas of responsibility, or “swim lanes,” with real job titles, descriptions, and KPIs for each co-founder.

Debates still happen. The rule that keeps them productive: “when we come to work, it’s professional mode, nothing’s personal.” One brother even left for a few years to do business development elsewhere — and rejoined six months ago, reuniting all three.

Cutting the fluff and working from the client’s P&L

Josh started Big Red Jelly partly out of frustration with big-agency inefficiency — vague line items like “strategy” and “creative” that clients pay for without seeing a practical benefit. His fix is to reverse-engineer every engagement from the client’s P&L: even a rebrand has to connect to conversion rates, the sales cycle, and revenue.

He’s candid that world-class freelancers are often the cheaper, more efficient option, which means an agency has to justify itself with outcomes: “everything that we do has got to impact the top and bottom line.” As performance marketing normalized paying for results rather than deliverables, that bar only got higher.

AI, GEO, and the rising value of human connection

Big Red Jelly now works with GEO (Generative Engine Optimization) — visibility in ChatGPT and Claude — alongside classic SEO. Josh’s framing, borrowed from Good to Great: technology is an accelerant. “It’s rocket fuel as opposed to gasoline” — AI amplifies whatever strategy, processes, and people you already have, good or bad.

Prospects increasingly show up with AI-built websites that get roughly “eighty percent of the way there.” The agency’s job is the last stretch: industry expertise, the right inputs, and turning a generic build into something that actually converts. In Josh’s view, the more AI does, the more clients crave a human who understands their business and simplifies a complicated landscape.

Agency pricing: bronze, silver, gold — then the shift to retainers

When COVID hit, about a third of Big Red Jelly’s recurring clients paused within a week. The team responded by niching down to one-time brand and build projects, priced in bronze/silver/gold tiers — guardrails for the sales team, with a deposit (ideally full payment) up front. Positioned correctly, more clients accept upfront payment than most founders expect.

Recently the agency pivoted again, leading with its ongoing “grow” service: two months up front, then a monthly retainer on a six- or twelve-month contract. “Recurring revenue is just such a nice thing” — easier to plan, staff, and schedule around.

Client red flags: earning the right to say no

As you grow, “you start to earn the right to say no more.” Josh’s number-one red flag: clients who hire experts and then dictate every move. His analogy — you don’t stand over a plumber’s shoulder telling him which screw to use. Holding that line, ironically, often closes more deals by establishing expert status.

Red flag number two: payment terms. Net-60 requests, no deposit, or “pay when it’s delivered” are dealbreakers now, even though they were tempting to accept in the early hustle years. For more on picking the right clients in the first place, see the client acquisition strategies agencies swear by.

Hiring when one role gets 800 applications

Both Vlad and Josh have watched job postings balloon from ~50 applicants to 700–800, with the same three or four genuinely suitable candidates. Josh’s filters: a walkthrough video inside the job description that answers all the usual first-call questions, then a simple ask — email your resume, portfolio, and a short video on why you’re a fit. Half never reply, filtering themselves out.

Big Red Jelly is also relaunching its paid internship program: three months is enough to see the intangibles — hard-working, smart, curious — and it doubles as a recruiting pipeline from Utah Valley’s talent pool.

Utah’s Silicon Slopes: edge or constraint?

Being in Utah rather than New York or LA is, on balance, an advantage: East and West Coast companies hire Big Red Jelly because it’s more affordable yet still US-based, and Silicon Slopes supplies talent and an entrepreneurial ecosystem. The trade-off is proximity to deal flow — Josh admits a year in NYC or LA would mean closing “deals like crazy.” His investor-style workaround: watch the next up-and-coming hubs, like Nashville, Charlotte, and Tampa Bay.

Advice for new founders

Starting over today, Josh would niche down faster, build strategic partnerships early, and spend his time on exactly two things: sales and marketing, and recruiting A-players. On the operational side of that, see when agencies should stop, restart, or hold the line and what running a digital agency actually teaches you.

For individuals entering the field, his bar is simple: technical skills get you the job, but “soft skills will get you promoted.” And the Big Red Jelly tagline that applies to any career: “be the best at everything that requires zero talent” — punctual, proactive, communicative, curious. Do that consistently, and you outpace most of your peers.

Find Josh at bigredjelly.com or on LinkedIn, and watch the full episode on YouTube.

When to Stop, Restart, Or Hold the Line: Agency Project Management With Brut And Superbase

We’ve covered decision-making in agency project management before – in our first piece on the topic, two agency leaders shared how they navigate project pivots and high-stakes calls. The responses were pointed enough that we decided to keep asking. This time, we brought the same questions to two very different teams: Brut Marketing, a boutique strategy and marketing agency operating between Bali and LA, and Superbase, an independent brand design and strategy firm based in Boise, Idaho.

Same questions. Different contexts. Genuinely different answers.

When Rebuilding Is The Smarter Move

Not every project can be salvaged by iteration. Sometimes the most efficient path forward is back to zero – and recognizing that early is its own skill.

Have you ever had to rebuild or redo a project from scratch? What led to that situation?

Dian Andrusary, Partner at Brut Marketing:

Yes – more than once. Usually, it happens when a project moves into design or promotion too quickly, before the foundation is really defined. A brand may already have a logo, a website, or some market activity, but the positioning is still blurry, the audience is too broad, or the product story is not sharp enough. In those cases, trying to “fix” things layer by layer often wastes more time than starting over with strategy and building properly from there.

Changing Course Mid-Project – and Knowing When It’s Necessary

Stopping a project mid-process is a harder call than it sounds. The work is already underway, time and money are in, and changing direction means admitting the original path wasn’t right.

Have you ever stopped a project mid-process because you believed the direction was wrong?

Dian: Yes – especially in product or service launches where the first goal is not to scale immediately, but to test viability. In those cases, we often go to market with an MVP version, a focused offer, and a set of working hypotheses around audience, positioning, and value proposition. Sometimes the market response shows that the initial assumption is simply not strong enough. When that happens, we would rather pause, step back, and rethink the core proposition than keep pushing a direction that is not being validated. For us, that is not failure – it is part of a strategic process.

Kelly Williams, Founder and Creative Director of Superbase:

Mid-project pivots aren’t uncommon, and can happen in varying degrees and for various reasons. For example, we’ve had projects that required drastic changes in the direction due to client name changes, trademark issues, or leadership changes on the client side. Of course, those are all external factors. As far as changing directions during a project because of some sort of evolution with the creative internally – yes, this has happened too. If, throughout the course of the project, we notice that something isn’t working or we receive new information that impacts the direction, we must adapt to this. Although it’s very rare, this can certainly happen, and we’re not too stubborn to admit if something isn’t working. We want to be proud of the work. So, if it becomes clear that we would not be proud of the work, we pause, re-evaluate, and adjust.

The Decisions That Shape Everything Else

Every project involves dozens of small calls, but a few carry disproportionate consequences – the ones that set the direction everything else follows.

What type of decision in your work carries the most responsibility or risk?

Dian: The most high-stakes decisions are always the early strategic ones: positioning, audience prioritisation, offer logic, and go-to-market direction. A visual mistake can usually be corrected. But a wrong strategic decision affects everything that comes after it – website structure, messaging, content, campaign mechanics, media budget, and ultimately how the market understands the brand. That is why we treat early-stage thinking with the same seriousness as final execution.

Kelly: I believe that our branding work requires the most planning, research, and insight. It can be a risky endeavor to start a new brand or undergo a rebrand. There can be a lot of resources invested into it. So, we try to help our clients understand that it is worthwhile to take the time necessary to do it right. Much of the responsibility is in the form of expectation management, and being able to navigate subjective topics in order to keep the work moving forward.

Owning Mistakes: How Agencies Handle Accountability

Things go wrong in every long-term client relationship. What distinguishes good agencies isn’t a perfect track record – it’s how they respond when something breaks.

How do you handle responsibility when a decision made by your team causes problems for the client?

Dian: First, we take responsibility quickly and directly. No hiding behind the process, no trying to soften the issue. Then we break the situation down very clearly: what happened, what impact it created, what can be fixed immediately, and what needs to change internally so it does not happen again. In our experience, clients can forgive mistakes much faster than they can forgive defensiveness or a vague response.

Kelly: As the founder and director of the studio, the responsibility always ultimately falls on my shoulders. So even if my team or a member of my team makes a call that causes a problem for the client, the client doesn’t view that as a one-on-one issue. It’s something that affects the entire business. I try to always stand by my teams’ decisions and support them, but if there is clearly a bad judgement call, Superbase owns up to it, and we adjust internally. If there is good chemistry with the client, we all understand that we are working together toward a common goal. Problems aren’t usually the result of only one decision. There is almost always a pattern or some underlying issues that can be discovered and resolved in order to avoid an impasse.

The Strangest Brief They’ve Ever Worked Around

Agency project management rarely stays within the lines of the original brief. Occasionally it goes somewhere nobody planned for.

What was the strangest or most unusual requirement you had to design or build around?

Dian: One of the more unusual challenges was working on a tennis platform that had to serve very different needs inside one ecosystem. It was not just about making a nice interface – the product had to combine booking, CRM functionality, web and app experiences, and features for both players and tennis businesses. The real challenge was making something quite complex feel intuitive and coherent for very different users. Projects like that force you to think beyond pages or screens and design around an entire system.

Kelly: This isn’t necessarily a design requirement, but as far as strange moments in my career – one that comes to mind was self-inflicted, actually. Working as the Creative Director for a footwear company at the time, I had this idea for a product photoshoot that would require some snakes slithering around the product. A reptile rental business in Southern California turned out to be the solution. The budget didn’t stretch to the optional snake handler, so I signed a waiver and opted to handle them myself. Snakes aren’t really my thing – but people in Hollywood do this kind of stuff all the time, so how hard could it be? Picking up a bunch of snakes and trying to bring out the supermodel in them was a pretty new experience, to say the least. They crawled all over me, but the project got done with no bites. Honestly, I’m convinced the snakes shared my sense of humor about the whole thing.

Final Thoughts

What stands out across both conversations is that strong agency leadership is rarely about always getting it right the first time. It’s about knowing when to pause, when to rebuild, when to defend a direction, and when to admit it no longer works. Whether it’s a boutique strategy team or an independent design studio, the common thread is a willingness to stay flexible without losing conviction. The best decisions in agency project management often happen long before launch day – in the uncomfortable moments where teams choose clarity over momentum, honesty over ego, and long-term outcomes over short-term convenience.

Explore More Agencies

If you’re an agency, designer, or startup looking to boost your visibility, you can join Norobots and become part of our curated network of trusted businesses. If you’re a brand or client searching for the right partner, our platform helps you discover agencies, designers, and startups you can rely on. Browse the listings and find the right fit for your next project!

Digital Agency Project Management: Making Decisions and Managing Risks

Decision-making in digital agency project management is rarely straightforward. Sometimes the right choice is to pause, change direction, or even rebuild part of the work entirely. In other cases, the biggest challenge is simply recognizing early that a project is drifting off course.

In this installment of our series, we take a closer look at how agencies approach those moments in practice – with insights from Growth Hackers, a digital marketing agency focused on data-driven growth strategies, and Betelguise Web Design, a UK-based web design studio specializing in tailored website solutions for businesses.

When a Project Needs a Fresh Start

Even in well-structured digital agency project management, there are times when continuing forward no longer makes sense.

Have you ever had to rebuild or redo a project from scratch? What led to that situation?

Paul Griffiths, Web Designer and Proprietor at Betelguise Web Design:

Luckily, no. We place a strong emphasis on getting a full and detailed brief from the client before starting any work, along with maintaining consistent communication throughout the project. This helps avoid major misalignment, so a complete rebuild has never been necessary.

Jonathan Aufray, CEO at Growth Hackers:

Yes, a few times. It usually happens when we realize halfway through that the initial strategy isn’t going to deliver the results we promised. It’s not an easy decision, but rather than pushing forward with something that falls short, we choose to rebuild. In the end, it allows us to deliver work that actually performs, instead of just ticking boxes.

Knowing When to Change Direction

Sometimes the clearest signal that something is wrong appears before the project is finished.

Have you ever stopped a project mid-process because you believed the direction was wrong?

Paul: Yes. In one case, despite having a full brief, it became clear that a key service of the client’s business had been overlooked – something that was essential for strong SEO performance. We guided the client through the issue and adjusted the direction accordingly, and the project was ultimately completed to their satisfaction.

Jonathan: Absolutely. Continuing would have meant wasting time and resources for both us and the client. It’s always better to pause, reassess, and pivot than to finish something that doesn’t create real impact. For instance, we were developing a content strategy for a wellness brand that relied heavily on long-form articles. Early engagement data showed that their audience preferred short, interactive content. We paused the project, shifted to video and social posts, and engagement doubled within weeks.

The Decisions That Carry the Most Weight

Some choices naturally come with higher stakes – especially those that directly affect performance, visibility, and growth.

What type of decision in your work carries the most responsibility or risk?

Paul: Creating a client’s online presence carries a significant level of responsibility, as it directly impacts how their business is perceived and found. That’s why clear and ongoing communication is key, ensuring that all content and decisions stay aligned with the agreed brief and overall goals.

Jonathan: Decisions that impact a client’s budget or overall growth strategy carry the most weight. A single misstep can affect not just performance, but also trust. That’s why we take a careful, data-informed approach and consider all angles before moving forward with major decisions.

Handling Mistakes in Digital Agency Project Management

When something goes wrong, the response matters just as much as the problem itself.

How do you handle responsibility when a decision made by your team causes problems for the client?

Jonathan: We take ownership immediately and communicate openly about what happened. That includes outlining a clear plan to fix the issue and taking extra steps to make sure it doesn’t happen again. Ultimately, our reputation depends not on avoiding every mistake, but on how we respond when something goes wrong.

Unusual Challenges in Agency Projects – and How to Tackle Them

At times, projects come with unexpected constraints that challenge teams to think differently.

What was the strangest or most unusual requirement you had to design or build around?

Paul: One of the more unusual projects involved a site selling adult products, which required a completely different approach to SEO compared to typical B2B or B2C work. It meant carefully adapting strategies to reach the right audience while navigating platform restrictions and sensitivities, making it a unique and interesting challenge.

Jonathan: We once worked with a client who needed an ad campaign that completely avoided using any of their brand colors because they were doing a very niche market test. It was an unusual constraint, but also a creative challenge. Finding a way to make the campaign effective within those limits ended up being a really fun and rewarding exercise for the team.

Final Thoughts

Project work rarely follows a perfectly linear path. From deciding when to start over to adapting strategies mid-process, the ability to make informed decisions is what keeps projects on track.

While every agency approaches workflow and decision-making differently, the common thread is clear: strong communication, flexibility, and a willingness to adjust course when needed are essential for long-term success. In an environment where priorities can shift quickly, these principles help agencies maintain both project quality and client trust.

Explore More Agencies

If you’re an agency, designer, or startup looking to boost your visibility, you can join Norobots and become part of our curated network of trusted businesses. If you’re a brand or client searching for the right partner, our platform helps you discover agencies, designers, and startups you can rely on. Browse the listings and find the right fit for your next project!