In Part 1, we built the foundation for a custom app in Method CRM. The example app tracks potential deals for an influencer or brand collaboration workflow. We created the app, built the list screen, created the new and edit screen, added table fields, and saved records back to the Opportunity table.
Part 2 is where we start refining the app so it fits the actual business process.
The first issue is the Stage dropdown. When you add the default Stage field from the Opportunity table, Method CRM brings in the standard opportunity stages. Those might work for a normal sales team, but they do not make sense for every custom app. If the app is tracking brand deals, internal projects, service requests, or any other custom workflow, the stages need to match that workflow.
In this guide, I will walk through how to manage dropdown stages in Method CRM by building a front-end stage editor. This gives users a clean way to add, rename, sort, and deactivate stages without digging through back-end configuration.
Start by Inspecting the Stage Field
Before you build a stage management screen, you need to understand where the Stage dropdown gets its values.
In the screen designer, click the Stage field and look at the field properties. In this example, the Stage dropdown is tied to the Opportunity Stage table.
That detail matters because the dropdown is not just a static list. It is reading from a related table. If you want to control the dropdown options properly, you need to manage the records in that table.
This is one of the reasons Method CRM customization is powerful. A dropdown can be driven by real data, not hardcoded values. That gives you more control, but it also means you need to understand the table behind the field.
Create a Stage Management Screen
The next step is to create a dedicated screen for managing stages.
In the app customization area, add a new screen and base it on the Opportunity Stage table. In the video, the screen is named New/Edit Stage because the goal is simple: give users one place to create and edit the stages that appear in the custom app.
A clean structure is enough:
- a header section
- a main section
- a footer section
- optional hidden controls if you need them later
Do not overcomplicate this screen. It exists to maintain a supporting list of dropdown values. The easier it is to use, the more likely the business will keep its stages clean.
Add a Header With Clear Navigation
The stage screen should feel connected to the rest of the custom app.
Add a back button, use a clear icon, and give the screen a title such as New/Edit Stage. Then add a simple bottom border or spacing so the header is visually separate from the main content.
These small design decisions matter. Users should know exactly where they are and how to get back. If a configuration screen feels hidden or confusing, people will avoid using it and the dropdown list will get messy again.
Use an Editable Grid for Stage Records
For the main section, use an editable grid.
A standard grid is good for viewing records. An editable grid is better when users need to maintain a small list directly on screen. In this case, the grid lets the user add or update stages without opening a separate record detail page for each one.
Configure the editable grid so it supports the way users should work:
- allow new rows to be added
- show only the fields that matter
- avoid unnecessary view selectors or page controls
- keep the layout focused on stage maintenance
For a stage list, the most useful fields are usually:
- Stage Order
- Stage Name
- Probability Percentage
- Is Not Active
That gives the business control over the dropdown label, the order of the stages, whether the stage is still available, and any probability logic used for forecasting or reporting.
Sort Stages With Stage Order
Stage order is one of the most important fields on this screen.
Without a sort order, dropdown values can appear in a sequence that does not match the real process. That creates friction every time someone fills out the form.
For a potential deal workflow, a simple sequence might look like this:
- Initial Outreach
- In Discussion
- Negotiation
- Closed Won
- Closed Lost
The exact names should come from the business process. The point is not to copy a generic sales pipeline. The point is to make the dropdown match how the team actually talks about the work.
When the stages are ordered properly, the dropdown becomes easier to scan and the app feels more intentional.
Use Probability When It Helps the Workflow
The Opportunity Stage table can also include probability.
That can be useful when the custom app is still deal-related, pipeline-related, or tied to forecasting. For example, an early stage might have a low probability, negotiation might have a higher probability, and closed won would be 100 percent.
You do not need to force probability into every custom app. If the workflow is not about sales likelihood, keep the screen focused on what matters. But when the app is tracking opportunities or potential revenue, probability can give you cleaner reporting later.
Good Method CRM builds are not just screens. They are data structures that support reporting, automation, and better decisions.
Deactivate Stages Instead of Deleting Them
One field I like to include is Is Not Active.
This lets users remove a stage from active use without deleting historical data. That distinction is important.
If a stage was used on old records, deleting it can create reporting problems or make past records harder to understand. Deactivating it is safer. The stage can stop appearing in the dropdown for new work, while old records still keep their historical context.
This is a good general rule in CRM design: archive or deactivate values when history matters. Do not delete business history just to clean up a dropdown.
Add Save and Back Logic
After the editable grid is in place, add a footer with a Save and Back button.
The button should save all changes and then return the user to the previous screen. This makes the stage maintenance flow simple:
- Open the Stage dropdown.
- Click the custom option to manage stages.
- Add, rename, sort, or deactivate stages.
- Save and return to the app.
The user should not need to understand the underlying table. They should just see a clean maintenance screen that does its job.
Connect the Stage Dropdown to the Management Screen
The most useful part of this build is connecting the Stage dropdown directly to the stage management screen.
In Method CRM, you can customize the dropdown row click behavior. In the video, the Stage field is configured with custom row text such as New/Edit Stage. When the user clicks that option, Method navigates to the stage management screen.
That turns the dropdown into more than a field. It becomes an entry point for maintaining the list behind the field.
This is a strong pattern for Method CRM custom apps. If a dropdown list needs business users to manage its values, give them a controlled front-end screen instead of making them ask an admin to change it every time.
Filter the Dropdown to Active Stages
Once users can deactivate stages, you need to make sure inactive stages do not keep appearing in the dropdown.
Add criteria to the Stage dropdown view so it only shows records where Is Not Active is false. Then sort by Stage Order so the values appear in the correct sequence.
This gives you a cleaner user experience:
- active stages appear in the dropdown
- inactive stages stay out of the way
- historical records can still retain old stage values
- the dropdown follows the order defined by the business
That is the difference between a quick customization and a durable one.
Why This Pattern Works
This stage management pattern works because it gives control to the right place.
The business can manage its own process labels. Users do not have to work around irrelevant default stages. Admins do not have to manually adjust dropdown values every time the process changes. And the app stays connected to Method CRM's underlying data model.
The same idea can be reused for other supporting lists in a custom app, including:
- lead sources
- opportunity types
- project statuses
- service categories
- cancellation reasons
- priority levels
If a list needs to be business-managed, build a simple front-end maintenance screen for it.
Common Mistakes to Avoid
Leaving the default stages in place
Default stages are fine when they match the process. If they do not, they create confusion. A custom app should use labels that make sense to the team using it.
Deleting old stages too aggressively
If records have already used a stage, deactivation is usually safer than deletion. Protect the history.
Forgetting to sort the dropdown
A dropdown with the right values in the wrong order still feels messy. Use Stage Order and sort the dropdown view by that field.
Giving users too many configuration fields
The stage management screen should stay focused. If users only need to manage name, order, probability, and active status, do not expose extra system fields.
Final Thoughts
Part 2 of building a custom app in Method CRM is about making the app fit the workflow, not just making it functional.
A Stage dropdown is a small field, but it carries a lot of operational meaning. When the stages are wrong, the app feels generic. When the stages match the business process, the app starts to feel like it was built for the team.
Build the stage management screen, use an editable grid, sort the stages, filter out inactive values, and connect the dropdown directly to the maintenance screen. That gives users a clean way to keep the app aligned with the business as the process changes.
If you are planning a deeper Method CRM customization, this is exactly the kind of structure you want early. The better your supporting tables and dropdowns are designed, the easier it becomes to add automation, reporting, and advanced workflows later.
If you want help designing a Method CRM app around the way your business actually works, book a free strategy call and let’s map it out.