Information technology
Technology is one of PNH’s two main fields. We design and implement software — and the other field is where it gets tested: the traceability, specification and scheduling problems in agriculture are the same problems software is good at, so we build for our own operations before we build for anyone else’s.
When you need us
These are the needs PNH is asked about most often. If your situation is different, talk to us and we will work out an approach that fits.
What we do
PNH looks into every requirement before proposing a solution. The scope of work, the deliverables and each side’s responsibilities are set out clearly from the start. If what you need is not among the services below, talk to us and we will work out an approach that fits.
A website that reflects the company properly and makes managing and updating content straightforward.
From company and product websites through to campaign pages, PNH works with you to settle the structure, content and experience before design and development begin.
A clear understanding of what you need before choosing or investing in a software solution.
PNH reviews your processes with you, identifies the problems worth solving and weighs the options that fit: adopting an existing solution, improving the current system, or building something new. Where it helps, PNH can stay alongside you through the implementation.
An application built around the business’s real needs and the way it actually operates.
From admin dashboards, portals and order management through to customer-facing and internal operating tools, PNH builds solutions that fit how they will be used rather than confining the business to a ready-made template.
Software development capacity when the business needs it, without expanding the in-house team.
PNH can take on a work item, a module or a defined part of the work, working alongside your existing team and handing over the full source code as agreed.
An application built from how customers and the business will actually use it.
iOS and Android development, with a technology approach chosen to suit each product’s features, users, operating capacity and direction of growth.
Your team understands the system, runs it, and steadily takes ownership of it.
Training tied to the real system and the real work, so the team gains the knowledge, tools and source code they need to run, maintain and develop the system after handover.
Bringing the company’s products and services closer to customers, right inside Zalo.
Zalo Mini Apps for ordering, booking, loyalty, customer care and other interactions, without building a separate standalone app. Reaching and serving customers on a platform they already use.
Know what is in each growing area, when it is due, and how much to expect.
Crop area software built from the work PNH already does each season: recording area and variety, tracking a season as it progresses, projecting harvest timing and volume, and keeping the traceability record that travels with each consignment.
Specialists added when your project needs more capacity.
People working directly alongside your team, following your processes and management arrangements for an agreed period.
How we work
The same shape whatever the service. What changes between a website and a placed team is the size of each stage, not whether it happens.
You describe what is going wrong today. We say whether this is work we should be doing, and whether software is even the right answer to it.
We look at how the work is done now, with the people who actually do it, and write down what the software has to do — and what it explicitly will not.
Cost and sequence against that scope, with the assumptions written beside them. If an assumption turns out to be wrong, you can see which number moves.
Work is delivered in pieces you can open and use, not held back for one reveal at the end. Priorities can change between increments.
Your people test it on real work before it goes live. Data is migrated, checked against the old system, and the switch is planned around your operations rather than ours.
Source code, documentation and training go to your team, and the support window is agreed in writing. The measure of a handover is whether you could take it to another supplier.
How we work
These apply whether the work is a single website or a team placed alongside yours.
Source code and intellectual property transfer to you. There is no component you have to keep paying us to hold, and no part of the system only we can change.
We write down what the work covers before quoting it. An estimate given before the scope is understood is a number chosen to win the conversation, not to be met.
Documentation is written as the work is delivered and the team is trained on the real system. The measure of a handover is whether you could take it to another supplier.
Questions
If the answer you need is not here, ask it directly — a question we cannot answer straight is worth knowing about early.
Next step
The most useful first conversation is about what is going wrong today, not about which technology to use. Send us that and we will tell you whether we are the right people for it.
We will review your information and reply once we have received your enquiry.
