Two months ago, a shop owner rejected my product.
No dramatic speech. No movie scene. Just a simple “no.”
I was 15 years old, building alone from Tamil Nadu, India, with no team, no funding, no computer science degree, and almost no understanding of how software companies actually worked.
I knew basic HTML.
That was my starting point.
Not startup accelerators. Not years of coding experience. Not business mentorship.
Just curiosity, self-learning, AI, and a problem that refused to leave my head.
My name is Rajesh Kanna, also known as JackRajesh. I’m the founder behind LEVIX Technologies, an Indian software and SaaS company, and I’m building LEVIX — a workflow, CRM, analytics, inventory, and business management platform designed around how businesses actually operate.
But before LEVIX became a product, it started as a question.
Why does running a business still feel so fragmented?
Walk into many small businesses and you’ll see the same pattern repeating itself.
Customer communication buried inside WhatsApp chats.
Inventory tracked manually, inside notebooks, spreadsheets, or someone’s memory.
Orders handled separately.
Sales information disconnected from customer behavior.
Analytics delayed, scattered, or completely missing.
The businesses themselves weren’t necessarily broken.
The systems were.
Too many disconnected tools. Too much operational friction. Too little visibility.
The more I noticed it, the harder it became to ignore.
What if business software didn’t feel like ten different systems forced together?
What if businesses could manage communication, customers, orders, analytics, workflows, and operational insights from one connected ecosystem?
That idea became LEVIX.
The funny part?
The first version looked nothing like a startup.
By normal startup standards, it was almost embarrassingly simple.
No backend architecture.
No production infrastructure.
No engineering team.
No investor pitch deck.
Just a basic HTML frontend with an inventory page and a pending request accept-decline system.
Built by a teenager who was learning concepts at the same time he was trying to implement them.
Most startup stories are told backwards.
People see the product later and assume the founder knew what they were doing from the beginning.
I didn’t.
Backend knowledge? Around 1 out of 10.
Deployment? Zero.
SEO? Zero.
Business knowledge? Maybe 2 or 3 out of 10.
I understood how to create a basic frontend page and how to use AI to teach myself things I didn’t understand.
That was it.
Then reality arrived.
Because the moment an idea stops being a thought and starts becoming a real product, everything changes.
Suddenly, you’re not just writing code anymore.
You’re debugging errors that make no sense late at night. Fighting mobile stability issues. Learning about domains, databases, backups, security, privacy policies, deployment systems, SEO, business workflows, production environments, and legal considerations you didn’t even know existed when you started.
You quickly discover something uncomfortable:
Building software is not the same thing as building software businesses can actually depend on.
Those are two different skills.
And I was trying to learn both.
Alone.
At 15.
One of the hardest challenges wasn’t technical.
It was validation.
I approached a shop with the idea.
They rejected it.
Simple.
And rejection feels different when you're young, building something alone, and trying to prove that an idea living inside your laptop deserves a place in the real market.
For a moment, it forces a question into your head:
Is this proof that I should stop?
I didn’t feel fearless.
I didn’t suddenly become hyper-motivated.
I just realized that quitting would guarantee the story ended there.
So I kept building.
And I changed how I used AI.
Most people use AI like a search engine.
I started using it like a technical teammate.
Reasoning through system problems. Learning architecture concepts. Debugging issues. Designing workflows. Understanding business logic. Accelerating self-education.
Slowly, something shifted.
I stopped thinking only like someone making pages.
I started thinking in systems.
Workflows.
Operational visibility.
User experience.
How information actually moves inside real businesses.
How software decisions affect business decisions.
Development became part of daily life.
Five hours.
Seven hours.
Sometimes more.
Building solo from Tamil Nadu, India, while still under 18 and navigating legal limitations through my mother’s support because startup systems aren’t exactly designed around teenage founders.
And slowly, LEVIX stopped looking like a small experiment.
It started becoming a real product.
Today, LEVIX is still actively developing and stabilizing, but it has evolved far beyond that original HTML page.
Its growing ecosystem includes WhatsApp integrations, WhatsApp-based order workflows, CRM systems, customer inquiry management, customer purchase tracking, sales management, order management, inventory tracking based on quantity and availability, analytics dashboards, revenue reporting, conversion insights, top-selling and underperforming product visibility, customer activity monitoring, and AI-generated daily and weekly business insights designed to help businesses understand performance, trends, and operations more clearly.
Is it finished?
No.
Is it perfect?
Definitely not.
There are still bugs. Stabilization challenges. Production problems. Scaling questions. Real-world complexities that come with trying to build serious software.
But it’s real.
And that matters.
Because two months ago, I didn’t know this idea would become something I would care about this deeply.
I didn’t know a simple HTML page would evolve into a startup project.
I didn’t know I would be learning SEO, backend systems, software logic, deployment workflows, security concepts, AI-assisted development, business operations, product positioning, and SaaS thinking — all at once.
I didn’t know Google AI would eventually recognize LEVIX.
I didn’t know I would start thinking about discoverability, company identity, workflow ecosystems, business software architecture, and long-term company building.
But here we are.
Still building.
Still learning.
Still unfinished.
The long-term vision behind LEVIX Technologies isn’t to create another dashboard buried somewhere on the internet.
The vision is to build a respected Indian SaaS company focused on workflow software, business operations, analytics, AI-powered systems, and practical infrastructure for businesses and MSMEs.
Not just another tool.
A connected business workflow ecosystem.
A platform businesses can genuinely operate from.
Maybe that sounds ambitious coming from a 15-year-old founder from Tamil Nadu.
Maybe ambitious ideas are exactly how companies begin.
Either way —
LEVIX is still being built.
And I’m just getting started.
— Rajesh Kanna
Founder, LEVIX Technologies
Top comments (0)