The system your business runs on

Built for how you actually work. Owned outright by you.

NyViA demonstration: a recorded exchange about cost and code ownership

NyViA Demo
Visitor

What does a build cost, and do I own the code?

NyViA

A focused tool is R60k to R180k, a full system R180k to R650k, and larger platforms R650k+. Yes, you own the source code, which is placed in your own repository from week one.

NyViA

If you tell me roughly what the system needs to do, I can give you a closer range, or put you in front of an engineer instead.

Ask NyViA about your own project

Scroll to open

Most companies rent their software. You get what everyone else gets, you wait in line for fixes, and the price goes up every year. LENCOE builds your system from scratch, designed around how your business actually works, and owned outright by you.

Typical engagement
Build
Client portal and billing
Stack
Node, PostgreSQL, React
Team
1 architect, 3 engineers
First demo
Week 3
You receive
Full source, in your repository
Licence fee
None

Every engagement is fixed price, agreed in writing before any code is written. The repository is yours from week one, not on handover, and you see working software every fortnight until it is done. How an engagement runs

The problem

Off-the-shelf software fits everybody. That’s the problem.

Every workaround your team has invented exists for a reason. The spreadsheet that shouldn’t exist. The same figures typed into two systems. The report somebody rebuilds every Monday morning.

None of that is a training problem. It happens because your software was built for somebody else’s business and you are paying to bend yours around it. We start from what your business actually does, then build to that.

Our main product

NyViA answers the question at 02:14, in your words, from your own material.

NyViA is a support and sales system that sits inside your website, your product or your WhatsApp. It learns your business, answers questions accurately, qualifies leads and passes the real opportunities to a person. It works every hour of every day and it never has a bad one.

Live

It knows your business, not the internet

We load NyViA with your products, prices, policies and the answers your team gives every day. It replies from that, in your tone of voice. When it does not know something, it says so and hands the conversation to a person instead of guessing.

  • Answers in the languages your customers use
  • Works on your site, in your app and on WhatsApp
  • Every conversation logged and searchable

Sorts real buyers from browsers

NyViA asks the qualifying questions your sales team would ask, then writes the lead straight into your CRM with the full conversation attached. Your people open the day with a list worth calling.

It tells you what customers keep asking for

Every conversation is a record of what people want, what confuses them and where they give up. NyViA groups that into plain reports, so you find out about the broken checkout step or the missing product line from your own data rather than from a complaint.

How NyViA works

Covers the hours you cannot staff

Most enquiries arrive outside office hours. NyViA handles them the moment they land, so nobody waits until Monday for an answer that takes ten seconds.

What it replaces

One person on live chat costs a salary, covers eight hours and handles one conversation at a time. NyViA covers twenty four, handles as many conversations as arrive at once, and costs a fraction of that. Your team stops answering the same forty questions and starts working on the ones that need a human.

24/7Cover
<10sFirst reply
∞At once
YoursConversation data

Ask it yourself

NyViA is answering on this page right now, from LENCOE’s own material. Ask it what a build costs, or who owns the code.

It answers from what LENCOE has given it. When it does not know, it says so and hands you to a person rather than guessing.

What we build

Custom software, built for how you actually operate.

We work across the whole stack, in open source and closed source, on your servers or ours. The right choice depends on your business, not on what we happen to prefer.

Engineers working together at a bank of monitors in a studio officeSoftware built around the work, not the other way round

Ownership

What you own when we are finished.

Plenty of firms build you a system and keep the keys. Here is exactly what changes hands on our projects, written down before we start.

The source code

All of it, in a repository you control, from the first week rather than the last. If you want to take it to another team tomorrow, you can.

The data

Your database, exportable in a standard format at any time, with no charge for leaving and no hostage clause in the contract.

The documentation

How it is built, how to run it, how to change it. Written for the engineer who inherits it, not as a formality.

No lock-in. We would rather keep your work by being good at it than by making it expensive to leave. Support is a separate agreement you can end. The system keeps running either way.

Security

Fewer moving parts means fewer ways in.

A typical off-the-shelf site runs dozens of add-ons written by strangers, on the same codebase as millions of other companies. When somebody finds a weakness in one of those add-ons, they have found it everywhere at once, and you wait for an unpaid volunteer to fix it.

We build with far fewer parts, and we know who wrote each one. Open source where it is well maintained and worth trusting, closed source where the work is yours alone. Everything gets reviewed by our team before it ships, and we patch on our schedule, not somebody else’s.

Engineers checking racked equipment in a data centre aisleYour servers or ours, your choice
  • Data stays where you need it. Your servers, your cloud account or ours. Your choice, and it can change later.
  • Access is limited and logged. People see what their job needs. Every change leaves a record.
  • Backups are tested, not assumed. A backup nobody has restored is not a backup.
  • Dependencies are reviewed. We check what we pull in, and we keep the list short.
  • We sign your NDA. Before the first conversation if you prefer.

The stack

What we build with, in the open.

Nothing exotic and nothing you cannot hire for. That is deliberate. Your system should be maintainable by any competent team, including one that is not us.

Front end

React
TypeScript
Vanilla JS

Back end

Node.js
PHP
Python

Data

PostgreSQL
MySQL
Redis

Hosting

AWS
Hetzner
Your own

Payments

Payfast
Stripe
Direct bank

Delivery

Git
CI pipelines
Staged releases

Close view of a circuit boardFewer parts, each one chosen deliberately

How a build runs

Four stages. You see working software in week three.

No six month silence followed by a reveal. You get something you can click on early, and you keep getting it every fortnight until the job is done.

01

We work out what you actually need

We sit with the people who will use the system and watch how the work happens now. Then we write down the scope, the price and the dates. Fixed, before anyone writes code.

Scope documentFixed quoteTimeline
02

We design it before we build it

Screen designs and the data model, agreed with you. Changing a drawing costs an afternoon. Changing a finished system costs a month.

Screen designsData modelSign off
03

We build in the open, every two weeks

You get a working version on a private link every fortnight, and a short call to walk through it. You correct course as we go instead of at the end.

Fortnightly demoTest environmentYour repository
04

We hand it over properly

Training for your team, written documentation, the source code and the keys. Then a support agreement if you want one, which you can end whenever you like.

TrainingDocumentationHandover

Our own work

We run our engineering on ourselves first.

Client work is under agreement and we do not publish names without permission. What we can show you is the software we built for ourselves, which is running in public right now.

NyViA

Our support and sales system. It is answering on this page right now, on our own content, with the same setup we deploy for clients. Open it and ask it something difficult.

In productionNodeLive here

The trading terminal

A subscriber platform with accounts, billing, live data and two trading engines running on real money. If our engineering could not hold up under that, we would not sell it to you.

In production2 live engines24/5

The client portal

Sign up, payments, subscription management and account controls, built in house rather than assembled from third party services that would hold our customer data.

In productionPayfastSelf hosted

Also from LENCOE

The FX trading terminal

A separate part of the business. We build trading software and run two engines on live markets, which is where a lot of our work on speed, reliability and risk controls gets tested hardest. It is a smaller line than our software work, and it is not for everyone.

Trading carries a high risk of loss and is not suitable for everyone. LENCOE supplies software only and never holds or trades client money.

2Live engines
3In development
24+Pairs watched
24/5Running

Payments handled by

Common questions

The things people ask us first.

It depends on the size of the job, so we give you a fixed quote before anything is built rather than an hourly rate that drifts. Small internal tools start in the tens of thousands of rand. Full platforms run higher. Tell us what you need on the contact page and we will come back with a real number within a working day.

You see working software in about three weeks. A focused internal tool is usually eight to twelve weeks end to end. A larger platform runs four to six months. We give you the dates up front and show you progress every fortnight, so you always know where things stand.

Yes, and it is written into the contract. The code sits in a repository you control from week one. You can take it to another team at any point, with no exit fee and nothing held back. We do not use licence terms that make leaving expensive.

Both, depending on what suits you. Open source tools that are well maintained and widely trusted save you money and make hiring easier. Closed source makes sense where the work is genuinely yours and you do not want it in public. We will tell you which applies to your project and why, in plain terms, before you decide.

We train your team, hand over the documentation and the keys, and then you choose. Some clients take a monthly support agreement for updates and fixes. Others run it themselves. Either is fine, and you can change your mind later. Nothing stops working if you stop paying us.

Usually, yes. NyViA connects to most common CRM, helpdesk and e-commerce platforms, and where there is no ready connection we build one. It does not require you to replace anything you are already running.

Yes, and we are happy to do it before the first proper conversation. Send us yours or ask for ours. We also do not publish client names or work without written permission, which is why this site shows our own systems rather than other people’s.

Next step

Tell us what is slowing your business down.

You do not need a specification or a budget worked out. Describe the problem in a few lines and we will tell you honestly whether it is worth building, roughly what it costs, and how long it takes.

Reply time
1 working day
First call
30 minutes, no charge
NDA
Signed on request
Quote
Fixed, before we build
Planning a build and want a rough cost and timeline? Ask me. I can answer questions about our work, or put you through to the team.