Our Joint Ventures
On some projects, we come in as a partner, not a contractor
- Home
- /
- Corporate
- /
- Our Joint Ventures
An idea's first form usually comes from inside an industry. Someone who's done the job for years can describe the problem, even picture what the solution should look like; the one thing they lack is the engineering to turn it into a working system. That's where we come in. On some jobs we do this for a fee; on others we sit at the table as a partner.
Our reason for choosing the second path isn't sentimental. Only someone who shares the risk asks the uncomfortable questions that determine whether a product will actually work: who's going to use it, why haven't they used it until now, whose job changes if it works. When those questions don't get asked at the proposal stage, the answers show up somewhere far more expensive.
Ventures start with R&D. We first check whether it's solvable, then put a small prototype in front of a real user — not a demo, actual use. Some ideas don't clear that bar, and there's nothing strange about that; we write down why a path closed, because that record becomes the starting knowledge for the next venture.
Our venture portfolio
A platform for camping and outdoor accommodation. Moved to the current version of the Netloji framework.
The engineering is ours, the industry knowledge is our partner's. That division is written down at the start of every venture.
Our partnership model
What we bring
The entire product side: data model, application, and interface; board design and field installation if the work has a physical side. Underneath sits the group's own development framework, content management, and content server — the venture doesn't build these from scratch, they're there from day one.
What we expect from you
The industry itself: real customers, real objections, and the instinct that comes from doing that job for years. A written idea isn't enough; we need a partner we can go into the field with.
How we start
With something small and working. We test it in front of a real user, not in a demo, and the decision to continue comes from that. If the first step demands a large investment, that's usually a sign the idea hasn't been narrowed down enough yet.
When we say no
We won't form a partnership if there's no access to the field, if the partner has no time to give the work, or if the idea only stands up with a large budget from the start. In those cases we suggest doing the work as a regular project instead.
Let's talk about working together
If you have a proposal or a question on this, let's start with a short conversation.