Choosing between a website, an app and an ERP is easier if you describe one work scenario. Who faces the problem, what do they do now and where do they lose time? The scope of the first version depends on the answer.
Corporate website
A website fits when a potential customer needs to quickly understand what services you provide and how to contact the team. In the United Building project, we put the services, construction projects and a request form on the public website. For a B2B company, it is useful to check whether a new visitor can find the right service and send a request from a phone.
Mobile app
An app makes sense when a user regularly does a task from a phone. For example, checks an order status or sends a report from a site. For the first version, pick one frequent scenario. Show a prototype to future users and see at which steps they need explanations.
ERP system
An ERP is worth considering when the same data is moved between spreadsheets or approval statuses are figured out in chats. Start with one process. For example, record who creates a purchase request, who approves it and where the decision is stored. Then define what data is needed at each step and which roles should see it.
What to prepare for a conversation with a developer
Take one real example and describe how it goes now. Then define the expected result and how to check it. For a website, this may be the share of visitors who get to sending a request. For an app, the time to complete a typical operation. For an ERP, the time from creating a request to its approval.
