Nayaro Labs · Innovate
Where we build our own things.
Labs is active from day one, not something we get to once the client work slows down. Products, internal tools, SaaS ideas, AI experiments and research — with an honest status on each.
What Labs is
A standing commitment, not spare time.
A services company that only ever bills hours never builds anything of its own. Labs is the deliberate counterweight: protected time for work that might not pay off.
Ideas taken far enough to be used by someone outside Nayaro.
Software small businesses can subscribe to instead of commissioning.
Testing where models earn their place in a real workflow.
The systems that run our own delivery, built for ourselves first.
Time deliberately spent on things that may not work out.
The status system
Four words, used literally.
Early-stage companies tend to describe an idea and a shipped product in the same tone. These labels exist so we cannot do that.
An idea we are testing on paper and in prototypes. It may not survive, and that is the point of this stage.
It survived. Someone is writing real code against a real use case, usually our own first.
In the hands of a small number of people outside Nayaro who agreed to put up with the rough edges.
Shipped, supported, and something we would be happy for a stranger to rely on.
The board
What is on it right now.
Updated as things move. When something reaches beta or live, it will say so here first — and until then, this page will keep saying that nothing has.
Nothing has shipped publicly yet. This is where it will show.
Delivery tooling
The systems we use to run our own projects — scoping, tracking, review and handover. Built for ourselves first, because we are the ones who feel it when it is wrong.
AI workflows for small businesses
Finding the places where a model removes hours of work each week — and the places where it quietly creates more. We test on our own work before offering it to anyone.
Student learning platform
Course material, project submissions and progress in one place for our own batches. If it works for us, it may be worth building properly for other teachers.
How an idea moves
Most of them do not.
The point of a process like this is to fail cheaply. Four stages, and three of them are opportunities to stop.
Someone hits the same wall twice
Almost everything here started as friction in our own work, or a problem a client described that turned out not to be theirs alone.
A week of finding out it is wrong
Before any real code, we try to kill the idea — who else solved it, what it would cost, and whether anyone would actually change their habits for it.
Built for ourselves first
If we would not use it daily, it does not get further. Being our own first user is the only honest early feedback available to us.
Out to a few people who will complain
A small beta with people who will tell us the truth. Most things stop here, and stopping is a legitimate outcome.
Work with Labs
Two ways in.
Labs is small, so both of these are limited. If either sounds like you, write to us and say which one and why.
Be a pilot user
If a project on the board is close to a problem you have, you can use it early and tell us where it fails. Free while it is rough, and you get a say in what gets built next.
Join a Labs project
Academy students whose work stands up, and developers who want to build something of their own, can be considered for a place on a Labs team. Ask — but bring something you have built.
For businesses
Tell us what you are trying to do.
Describe the problem in plain language. If we are the wrong people for it, we will tell you that instead of quoting for it.
Start a ProjectFor students
Come and learn to build.
Ask about the next batch, what a laptop needs to run, and what you would actually be building in the first month.
Explore Academy