From Opportunity to Profitability: Connecting People, Projects and Billing with ERPNext

In a manufacturing company, ERP follows materials. In a manpower-driven service company, ERP needs to follow people.

A customer requirement may begin as an opportunity for five engineers. But fulfilling that opportunity can involve Sales, Recruitment, HR, Project Management, Attendance, Timesheets, Payroll and Finance. The real challenge isn't managing each activity separately.

It's connecting them.

That is the challenge we encountered while implementing ERPNext for engineering, technology and project-driven service businesses — and it led us to think about ERP differently.

The Business That Doesn't Sell a Product

Many engineering and service companies don't sell physical products. Their biggest asset — and often their biggest cost — is people. A customer requirement comes in. The company needs to understand the skills and number of people required, identify available resources or recruit new ones, deploy them to the customer or project, track their work, manage salaries and vendor costs, bill the customer and eventually understand the commercial performance of that engagement.

In many organisations, these activities don't live in the same system. Sales manages opportunities in CRM. Recruitment works through spreadsheets and emails. HR maintains employee information. Project managers track deployments separately. Employees submit attendance and timesheets. Finance prepares invoices using information collected from different teams.

Management then has to bring all of this together to answer a simple question:

How is this engagement actually performing?

The problem isn't necessarily with any individual department.

The problem is the gap between them — and those gaps can eventually affect utilisation, billing and margins.

The ERP opportunity is therefore not simply to automate each department.

It is to connect them into one commercial and operational lifecycle.

From Opportunity to Profitability

The entire business model can be understood through one flow:

Opportunity → Resource Requirement → Resource Pool / Recruitment / Vendor → Project Deployment → Attendance & Timesheet → Customer Billing → Payroll / Vendor Cost → Project Contribution

This is the journey ERP needs to follow. Project contribution — the revenue from an engagement minus the resource and vendor cost of delivering it — is what ultimately determines whether that engagement is profitable. The individual modules are important, but the real value comes from the connections between them.

Sales Doesn't End When the Opportunity Is Won

In a manpower or engineering-services company, an opportunity represents more than potential revenue.

A customer may require five verification engineers for six months, a team of field engineers for a telecom project, or an entire engineering team for a fixed-price assignment.

The requirement may include:

1. Number of resources
2. Required skills and experience
3. Expected start date
4. Duration
5. Business unit
6. Customer/project
7. Commercial rates

Once the opportunity progresses, that information shouldn't remain only inside the sales pipeline.

It needs to become a resource requirement.

That creates one of the most important connections in this business model:

Sales → Resource Planning

A sales commitment now becomes something the delivery, recruitment and HR teams can actually act on.

From Resource Requirement to Recruitment

The next question is simple:

Do we already have the people?

Before starting recruitment, the organisation should ideally be able to answer:

1. Who is available?
2. Who is on the bench?
3. Who is already deployed?
4. What skills do they have?
5. When will they become available?

If the required resource is available internally, that person can be considered for the engagement.

If not, the resource gap can trigger recruitment.

The journey becomes:

Customer Requirement → Resource Gap → Job Opening → Recruitment → Selection → Onboarding → Deployment

This changes the role of recruitment.

A requirement for two engineers is no longer simply an HR vacancy.

It represents capacity required to fulfil a customer commitment.

If the customer requires five engineers and only three are available, the remaining two positions have a direct relationship with project delivery and potential revenue.

Hiring starts from business demand.

One Person, Two Business Identities

This is one of the most important distinctions in a manpower-driven business.

Internally, someone is an employee.

Commercially, that same person may be a billable resource assigned to a customer or project.

The ERP needs to connect both views.

When these views are disconnected, the same person may effectively exist as separate records across HR, Projects and Finance.

When they're connected, management gets a much clearer relationship between people, projects, costs and revenue.

That is where ERP begins to become commercially useful rather than simply administratively useful.

Different Commercial Models, One System

Engineering and project-based service companies rarely operate with only one billing model.

The same organisation may have several.

Time & Material (T&M)

Billing may depend on the resource, approved time and agreed billing rate.

The important connection becomes:

Resource → Timesheet → Approved Billable Time → Customer Billing

Dedicated Resource / Offshore Development Centre (ODC)

A person or team may be dedicated to a customer for an agreed period, usually with monthly commercials.

Here, deployment dates, availability, utilisation and commercial terms become important.

Fixed-Price Projects

Billing follows agreed project milestones or commercial terms rather than individual hours.

However, the effort and project-related costs still need to be tracked against the engagement so management can understand project performance.

ERP therefore needs to understand more than who is working.

It needs to understand:

How does this engagement earn revenue?

ERPNext already provides the foundation for linking projects with tasks, timesheets, sales, expenses and billing. The implementation challenge is designing those elements around the actual commercial model of the business.

Vendor Manpower Belongs in the Same Picture

Not every customer requirement is fulfilled using employees on the company's own payroll.

Project-driven businesses frequently use external consultants, contractors and resources supplied by other vendors.

Operationally, those people may work on the same customer project as internal employees.

Commercially, however, their cost is different.

The basic relationship becomes:

Customer Revenue – Resource / Vendor Cost = Contribution from the Engagement

If vendor manpower sits outside the project system, part of the commercial picture is missing.

External resources therefore need to remain connected to the relevant customer, project, deployment and commercial arrangement.

The objective isn't simply to know who is working on the project.

It is to understand the commercial relationship behind that resource.

Attendance, Timesheets, Payroll and Billing Tell Different Parts of the Same Story

These terms are sometimes treated as though they represent the same information.

They don't.

Attendance answers: Was the employee working?

Timesheet answers: Which customer or project did the employee work for?

Payroll answers: What did that employee cost the organisation?

Billing answers: What did that work earn?

Each is useful individually.

But when they are disconnected, management still needs to combine multiple reports to understand the engagement.

When connected, they can provide a much clearer per-project, per-customer and per-resource view of effort, cost and revenue.

That is where the business starts moving from departmental reporting towards operational visibility.

Different Industries. A Very Similar Business Problem.

We have seen this model across very different industries.

In a semiconductor engineering services company, the resource may be a design, verification or embedded engineer.

In a telecom, IT infrastructure or managed-services company, it may be a field engineer, technician or project resource.

The technical skills are completely different.

But the commercial journey can be remarkably similar:

Identify the requirement → Find the right people → Deploy them → Track the work → Bill the customer → Understand the contribution

That is why this approach is relevant beyond traditional IT services.

It can apply to engineering services, semiconductor and hardware design companies, telecom contractors, managed-service businesses, technical staffing companies and other project-based organisations where people are central to delivery.

The Management Question Changes

Once the chain is connected, management starts asking better questions.

Instead of only:

How many employees do we have?

The questions become:

1. How many are currently billable?
2. How many are on the bench?
3. Which projects need additional resources?
4. Which skills are we currently short of?
5. What is our resource utilisation?
6. Which customers are consuming the most effort?
7. What is coming up for billing?
8. What are our internal and vendor resource costs?
9. How are individual projects and engagements performing commercially?

These aren't purely HR questions.

They aren't purely project-management questions.

And they aren't purely finance questions.

They are business questions.

Answering them requires the entire chain to be connected.

This Is Different From Implementing ERP Module by Module

A traditional ERP implementation can easily become a collection of modules.

CRM gets configured.

HR gets configured.

Projects gets configured.

Accounts gets configured.

Every department may get better software, but management can still end up bringing information together manually.

For a manpower-driven business, we believe the better starting point is the business chain.

The opportunity should create visibility of the resource requirement.

The resource requirement should connect with internal availability or recruitment.

Recruitment should end with a resource that can be deployed.

Deployment should connect that resource to the customer and project.

Timesheets should connect work performed with the engagement.

Billing should follow the commercial model.

Employee and vendor costs should contribute to understanding project performance.

When these connections are designed properly, management reporting becomes a natural outcome of the process.

Without them, we may simply have automated the individual fragments.

What Actually Changes

So what really changes?

The sales team still sells.

Recruiters still recruit.

HR still manages employees.

Engineers still deliver.

Project managers still manage projects.

Finance still invoices customers.

The difference is that these activities no longer have to exist as isolated events.

A customer requirement can be followed from the original opportunity through resource planning, recruitment or allocation, deployment, project execution and eventually billing and commercial performance.

In manufacturing, ERP can follow the journey of material.

In a manpower-driven business, it needs to follow the journey of a customer requirement and the people assigned to fulfil it.

That is the real opportunity.

Connect the opportunity. Connect the people. Connect the project. Connect the money.

And suddenly ERP isn't just recording what the business did.

It starts helping management understand how the business works.

Built for Project and Manpower-Driven Businesses

At Wahni, our approach to ERPNext implementation starts with understanding the business model before configuring the modules.

As an official Frappe partner, we have worked with engineering, technology, telecom and project-driven service businesses where people, projects and commercial models need to work together.

The objective is not simply to implement CRM, HR, Projects, Payroll and Accounts.

It is to connect them around the way the business actually earns revenue.

Whether your organisation operates through T&M resources, dedicated teams, fixed-price projects, vendor manpower or a combination of these models, the ERP should give both the operational team and management a connected view of the engagement.

Read how the same connected approach applies to contracting companies.

Looking to connect your opportunity-to-profitability journey with ERPNext? Talk to Wahni about your business process.

Frequently Asked Questions

What kind of companies is this solution suitable for?

This approach is particularly relevant for project-based and manpower-driven organisations such as engineering services companies, semiconductor and hardware design services, telecom and IT infrastructure contractors, managed-service companies and technical staffing businesses.

Can ERPNext support T&M, dedicated-resource and fixed-price projects?

Yes. Different commercial models can coexist within the same organisation. The important part is designing the project, timesheet, billing and financial workflows around the commercial terms of each engagement.

How can recruitment be connected to project requirements?

A resource shortage identified against a customer or project requirement can trigger recruitment. Once the candidate is selected and onboarded, the resulting employee can become available for allocation to the relevant engagement.

How do timesheets, attendance and payroll work together?

They answer different questions from the same source of truth. Attendance records whether an employee was working; timesheets record which customer or project the time was spent on; payroll records what that employee cost the organisation; billing records what the work earned. Connected, they produce a per-project, per-customer and per-resource view of effort, cost and revenue instead of four disconnected reports.

Can external or vendor-supplied manpower be managed alongside employees?

Yes. Vendor and external resources can be associated with projects and customer engagements while retaining their separate commercial and cost arrangements. This allows internal and external resources to be considered as part of the same delivery picture.

This article draws on Wahni's ERPNext implementation experience with engineering, technology, telecom and project-driven service businesses. Client-specific workflows and commercial information are not disclosed.