Passagens Europa
A CRM that brings together leads, customer support, quotes, finance and commissions for a sales operation.
See the Passagens Europa caseCustom systems for the way your company works.
EDevsHub builds custom management systems, CRMs and dashboards. The starting point is understanding who uses the process, which rules it must follow and what is currently scattered across spreadsheets and tools.
- Technical lead: Eduardo Gouveia, Senior Full Stack Developer
- Workana HERO
- 187 completed projects
- Profile checked on 29/10/2026
When the workflow doesn’t fit your current tools.
- The same information is retyped in different trackers and nobody knows which one is up to date.
- The operation has stages, approvals or exceptions that the current tool cannot represent.
- There is a system in use, but it lacks a module or a view for the people who follow the work.
Build a whole system or complete what already exists?
The first decision is the size of the intervention. Sometimes integrating tools or adding a module is enough. When the operation’s rules require an application of its own, the essential flow is separated from the improvements that can wait for another stage. That defines a scope that can be described and validated.
The scope starts with the work that needs to happen.
These are examples of deliverables and acceptance criteria. The proposal defines which ones go into your project and how they will be checked.
Stages and owners
Represent a sales or operational process, with states, owners and a history of changes.
Acceptance example: An authorized user moves a record between the agreed stages; the system records who changed it and when.
Access roles
Define what each role can view, create and change, based on the real workflow.
Acceptance example: The allowed actions work for each role; unauthorized operations are also blocked on the server.
Dashboards and queries
Organize the information the team needs to follow pending items and make decisions.
Acceptance example: Filters and totals are checked against a known set of records, including cases with no results.
Imports and integrations
Plan how existing data comes in and how the system relates to services that stay in use, when that is part of the project.
Acceptance example: A sample is imported and checked; duplicates and invalid data get the agreed treatment.
From the portfolio
A related solution.
How the work is organized.
Map the workflow
Understand a concrete flow, its users, documents and exceptions. Identify what can already be reused.
Define screens and rules
Agree on deliverables, permissions, acceptance criteria and dependencies before development.
Validate in stages
Show the flow working so it can be checked against real scenarios from the operation.
Prepare the delivery
Check the agreed criteria and carry out the knowledge transfer and release defined in the scope.
Before defining the project.
Do I need to replace all my tools?
Not necessarily. EDevsHub can evaluate an additional module or an integration. The choice depends on the current limitations, the available access and the rule that needs to be met.
Does EDevsHub also work on an existing system?
Yes. To define the work, we need to know the code, the infrastructure and the problem to solve. That assessment separates the requested change from any technical dependencies.
Can the data from spreadsheets be imported?
Importing can be part of the scope. First, the format, quality, volume and matching rules need to be checked. The validation process and who is responsible for checking are agreed in the proposal.
Are maintenance and support included?
What will be delivered, the documentation, the planned adjustments and any support must be stated in the proposal. Later improvements can be organized as another scope; this page does not assume any support period.
Show us one workflow from your operation.
Prefer to hire through Workana? See the profile. If the conversation already started on Workana, send the context in the same chat.
To start the conversation, it helps to gather:
- What the team does today and where it records the information.
- Who uses the process and which difficulty needs to be solved first.
- The existing tools and any access or timeline constraints.