Website design
A website that represents the business properly and can be updated without a developer.
Company, product and campaign websites — structure and content model settled first, then the design and the build on top of it.
Read more
Information technology
Software built for the people who have to run it afterwards
Alongside our agricultural business we design and implement software. The two are less separate than they look: the traceability, specification and scheduling problems in agriculture are the same problems software is good at, and we build for our own operations before we build for anyone else’s.
Who this is for
Most of this work starts from one of these
If none of them describes you, the work is probably still within scope — these are the situations we are asked about most, not the limits of what we take on.
- Running the business on spreadsheets that have outgrown it
- A website that no longer represents the company
- A system in place, but no capacity to extend it
- Reaching customers who live inside Zalo
- A process that only works because one person remembers it
- A team that needs to take over software someone else built
What we do
Eight services, each with a defined scope
Every engagement starts with what you get and what it includes, written down. If a requirement does not fit one of these, say so — a scope invented to match a service list helps nobody.
Software consulting and implementation
A decision about what to build, buy or change that you can defend — and the implementation that follows it.
Reviewing how the work is done now, specifying what the software actually has to do, and running the implementation through to live use.
Read more
Web application development
An internal or customer-facing application that fits how the business actually works.
Custom web applications — dashboards, portals, order and inventory tools — built to the process rather than the process bent to fit a package.
Read more
Software outsourcing
Delivery capacity added without hiring, on work whose source and rights stay yours.
Taking a defined scope of software work end to end, or running an agreed part of an existing roadmap alongside your own team.
Read more
Mobile app development
An app your customers or staff will keep on their phone rather than delete in a week.
iOS and Android applications, built natively or cross-platform depending on what the app has to do — not on what is fashionable.
Read more
IT training
People on your team who can maintain and extend what was built.
Practical training for teams taking on a new system, delivered on the tools and the codebase they will actually work in.
Read more
Zalo Mini App
A presence inside the app most Vietnamese customers already have open.
Zalo Mini Apps for ordering, booking, loyalty and customer care — reaching customers without asking them to install anything.
Read more
IT resourcing
The specific skills a project needs, for exactly as long as it needs them.
Developers, testers and technical specialists placed into your team, working to your process and reporting to your leads.
Read more
How we work
Six stages from first conversation to handover
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.
First conversation
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.
- You give
- The problem in your own words
- You get
- A straight answer about fit, including no
Scope
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.
- You give
- Time with the people doing the work
- You get
- A written scope, including what is out of it
Plan and estimate
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.
- You give
- Your decision on the scope
- You get
- A phased plan, a price, and the assumptions behind both
Build in increments
Work is delivered in pieces you can open and use, not held back for one reveal at the end. Priorities can change between increments.
- You give
- One person who can answer questions
- You get
- Something usable at the end of each increment
Testing and go-live
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.
- You give
- Your sign-off and the data to migrate
- You get
- The system live, with the migration verified
Handover and support
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.
- You give
- The team who will run it
- You get
- Source, documentation, training and an agreed support window
How we work
What we commit to on every engagement
These apply whether the work is a single website or a team placed alongside yours.
You own what we build
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.
Scope before estimate
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.
Built to be handed over
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
Questions we are asked before the first meeting
If the answer you need is not here, ask it directly — a question we cannot answer straight is worth knowing about early.
You are an agricultural company. Why are you writing software?
Because we needed it ourselves. Traceability, specifications, scheduling and stock are software problems before they are agricultural ones, and the team that builds for our own operations is the team that builds for clients. Agriculture remains our main business; this is a second one, run properly rather than as a side line.
Do you work with businesses outside agriculture?
Yes. Nothing in the list of services is specific to agriculture, and most of it — websites, internal applications, mobile apps, resourcing — is the same work in any industry. Where our own sector does help is when a client is moving physical goods, because we have had to solve those problems for ourselves.
Who owns the code when the work is finished?
You do. Source code and intellectual property transfer to you, and the handover includes the documentation needed to run it. There is no component we keep hold of, and nothing in the system that only we can change.
How is the work priced?
Two ways, depending on how firm the scope is. A fixed price against a written scope where the requirement is settled, or an agreed monthly rate for a dedicated team where it is still moving. We will tell you which one fits and why. We do not quote before the scope is written down, because a number given earlier than that is chosen to win the conversation rather than to be met.
Can you take over a system somebody else built?
Often, yes — but only after reading it. We start with a paid review of the code, the data and how it is deployed, and report back on what it would take to maintain or extend it. That report is yours whether or not you continue with us. Agreeing to take over an unseen system is how both sides end up in a difficult position.
We do not know what we need yet. Is it too early to talk?
No — that is the right time. The first stage is a conversation about the problem, not the solution, and it costs you nothing. If it turns out that what you need is a change to a process rather than software, we would rather say so than sell you a system.
Next step
Tell us the problem before the solution
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 reply to every enquiry within one working day.