Guide6 min readUpdated
Design Support After Launch: Updates, Fixes and New Features
How design support after launch works: small updates, fixes, new features and new creatives. See what to send, how it is quoted and what to expect back.
By Tithi Mondal, UI/UX Designer
Suppose your restaurant app went live last month. Orders are coming in. Then three things happen in one week: Diwali is near and you want a festival banner, customers keep missing the "Add note" box at checkout, and your owner asks for a table booking feature. The design is "finished", but the work is not over. This guide explains how design support after launch works, so these requests do not become confusing.
Design support after launch means getting design help for a product that is already live: small changes, fixes, new features and new visual material. A launch is not the end of design. Real users show you problems that no meeting could predict. Here is how to handle each kind of request.
What kinds of design work come up after launch?
Four kinds of work come up most: small updates, usability fixes, new features and new creatives. Each one has a different size and a different way of being priced.
| Type of request | Example | Typical size | How I quote it |
|---|---|---|---|
| Small update | Change a banner, a label or a colour | One or two screens | Custom quote for UI/UX work, based on screens |
| Usability fix | Make a hidden button easier to find | A few screens | Custom quote, based on screens |
| New feature | Add table booking or a new user role | A new flow of several screens | Custom quote, based on screens and user roles |
| New creatives | Festival posts, new icons, a new slide deck | A set of items | Fixed prices for posts, icons and presentations |
In every case, the request begins with a message and ends with files in the same style as your existing design. Payment on a new piece of work follows my usual terms, which are 50% to begin and 50% on completion, unless we agree a different plan in writing.
How do small design updates after launch work?
A small update is a limited change to screens that already exist, such as new text, a new image or a changed button. It is the fastest kind of post-launch work, because the design system is already in place.
To make a small update quick, send me:
- A screenshot of the current screen, with the area marked
- The new text, image or colour, ready to use
- The date by which it must be live
- A line about why you want the change
The last line matters. "Make the button bigger" is an instruction. "Customers miss the button" is a problem, and a problem gives me room to find a better answer than a bigger button.
For visual material such as banners, read the festival creatives design guide and plan the dates early. Festival posts for Durga Puja, Diwali or Eid need time, and everyone else is asking for the same week.
How do I handle design problems that show up after real users arrive?
Handle them by collecting evidence first, then asking for a fix. Real user behaviour tells you which screens need work, so do not change screens based on one complaint.
A simple way to gather evidence:
- Write down every complaint about a screen, with the date and the phone type if you know it.
- Look for the same complaint three or four times.
- Send me the pattern, not each single message.
- Watch two or three real users use the screen, if you can.
If three delivery partners cannot find the "Mark delivered" button, that is a design problem. If one customer dislikes a colour, that is an opinion. The guide on usability testing on a small budget shows how to watch users without a lab, and the UX audit checklist helps you review a live product step by step.
Also check whether the problem is design or code. A button that is too small is a design issue. A button that does nothing when tapped is usually a bug for your developer. I can help you describe the issue correctly, which saves time for both people.
How are new features designed after the app is live?
A new feature is designed as a small version of the original project: understand, map the flow, wireframe, design and hand off. It must fit the style and the structure of the screens already live.
The earlier work helps here. Your Figma files from the first project hold the colours, type and components. So a new feature does not start from zero, and the new screens look like they belong. If you do not have a shared set of styles, design system for startups explains why one saves money over time.
Before you ask for a new feature, answer three questions:
- Which users need it, and what problem does it solve?
- Where does it fit in the current navigation?
- What must change on existing screens to make room?
A feature such as table booking is more than one screen. It needs a date picker, a confirmation, a booking list and perhaps a message through WhatsApp. To decide whether your changes are large enough to need a bigger rethink, read app redesign or rebuild.
New features are quoted by the number of screens and user roles, just like the first project. Timelines depend on the size. A small feature takes less time than the 2 to 4 weeks of a full app or website design.
What should I keep ready so support requests go smoothly?
Keep four things ready: your Figma files, your brand files, a list of known issues and a way to reach your designer. With these, a small request does not need a long explanation.
Make a simple folder, shared with whoever manages your product:
- The final design files from the project
- Your logo files and brand colours, see what files to ask your designer for
- A running list of change requests, with screenshots
- The names of fonts used, so new material matches
Keep one running list rather than sending a message for every small idea. Once a week or once a fortnight, send the full list. I can then sort it by size and tell you what to do first. This also makes the quote clearer, because a batch of small changes is easier to price than ten separate messages.
Your developer needs the latest designs too. Use the Figma developer handoff checklist every time a new feature goes to code, so that old screens and new screens do not get mixed up.
When should I plan ongoing support instead of one-off requests?
Plan ongoing support when you send design requests every month, not once in a while. A regular arrangement saves you the effort of starting a new conversation every time.
If you only need a festival banner twice a year, one-off requests are fine. If you post on social media every week, update your app every month and add features every quarter, a regular arrangement is more practical. I give a custom quote for ongoing work, based on what you need each month.
You can also prevent many small requests by checking the product before launch. The app launch design checklist and the website launch checklist catch the problems that customers would otherwise find for you.
If your product is live and you need changes, tell me what you see and what you want to improve through the contact section, or look at my UI/UX design service.
Frequently asked questions
Can I ask my designer for changes after my app is live?
Yes. Send a screenshot, the goal and the date, and I reply within 24 hours. Each change is treated as a small new piece of work with its own quote.
Are post-launch changes covered by the revision rounds?
The 2 to 3 revision rounds belong to the original project. Work after launch is a new request, so I quote it separately.
How are new features priced after launch?
A new feature is quoted by the number of screens and user roles, like the first project. Posts and icons use my fixed per-item prices.
Is a bug the same as a design change?
No. A bug means something does not work, and your developer fixes it. A design change means something works but confuses users, and a designer fixes that.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.