How to Brief a Nigerian Agency on a Redesign or Rebuild of Existing Software

Your existing software is slow, buggy, or just ugly. You want to hire a Nigerian agency to redesign or rebuild it. But if your brief is vague, you will get the same problems in a different wrapper.

Learning how to brief a Nigerian agency on a software redesign is the difference between a successful project and a second failed one. A clear brief sets expectations, defines scope, and saves you from endless change requests.

Start With What Is Broken, Not What You Want

Before you list new features, document everything wrong with the current software. Is it slow? Does it crash on certain devices? Do users abandon the checkout page? Be specific. Instead of saying "the app is slow," say "the dashboard takes 12 seconds to load when there are 500 users."

This gives the agency real problems to solve. When you brief a Nigerian agency for a software redesign, your pain points are more valuable than your wish list. The agency can propose solutions you never considered once they understand the actual issues.

Include Technical Context About the Existing System

Share what you know about the current technology. What programming language was it built with? Who hosts it? Do you have the source code? Is there a database schema or API documentation?

If you do not have this information, say so. The agency can perform a technical audit as the first phase of the project. This upfront discovery phase prevents surprises halfway through the redesign when someone discovers that critical data is locked in an undocumented format.

Define What Success Looks Like

Your brief must answer one question: how will you know the project is done? Set concrete success criteria. For example, "the new checkout page must load in under 2 seconds on 4G networks in Lagos" or "the admin dashboard must support 1,000 concurrent users without crashing."

These numbers become the benchmark for acceptance testing. Without them, the agency may deliver a beautifully designed app that still performs poorly, and you will have no objective way to reject it.

Separate Redesign from Rebuild in Your Brief

Be clear about which one you need. A redesign changes the user interface and user experience while keeping the existing codebase. A rebuild throws away the old code and writes fresh code that replicates the same business logic.

If your current code is poorly structured, a redesign will be frustrating and expensive because every UI change requires fighting with bad code. In that case, a rebuild is the better investment. Your brief should state your preference and invite the agency to challenge it based on their technical assessment.

Common Misconceptions

Misconception 1: You need to know exactly what every screen should look like

You do not need to be a designer. You just need to describe what each screen should do and what information it must display. The agency's designer will turn that into wireframes and mockups that you approve before development starts.

Misconception 2: The new agency can just copy the old design

A redesign implies improvement. Copying the old design defeats the purpose. Give the agency freedom to rethink the user experience, as long as the core functionality stays intact.

Misconception 3: A detailed brief means the project will cost more

A detailed brief reduces risk for the agency, which often leads to lower and more accurate quotes. The agency can plan better when they know exactly what they are dealing with. Ambiguity drives prices up because the agency has to pad for unknowns.

Frequently Asked Questions