CRM
Every customer conversation in one place, and a pipeline you can forecast from.
OpenSoftware product
ERP
One system where finance, stock, purchasing and sales read from the same numbers.
The catalogue
What the product does
Enterprise resource planning fitted to the way the business already runs — scoped by industry, budget and the people who will operate it, rather than switched on whole.
- Finance, purchasing, inventory and sales on one set of data
- Modules brought in by phase, in the order the business needs them
- Migration from the spreadsheets and systems in use today
- Roles and permissions that match how responsibility is actually split
- Reports built with the people who have to read them
What it looks like
The software, not a description of it
Who this is for
Who this is for
The situations this product was built for. If none of them is yours it does not mean no — it means ask.
- Businesses running every function on a separate system
- Companies where closing the month takes days of reconciliation
- Operations that have outgrown off-the-shelf accounting
How we work
How an implementation starts
The first three stages. Implementing a product runs the same way as building one: scope first, then a plan you can hold us to.
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
Questions
Questions we are asked before the first meeting
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.
Other software products
Production management (MRP)
A production plan that reflects real capacity, with materials ordered against it.
OpenWork management
Everyone can see what they own, what is late, and what is waiting on them.
Open
Next step
ERP
Describe how this work is done in your business today. You will get a straight answer about whether this product fits, and what implementing it would involve.
We reply to every enquiry within one working day.