Inside Team Incrix: How a 15-Person Team Builds Software, Hardware and Products Together

Most people who meet us expect a much bigger company.

They see a multi-tenant LMS in production, a family of ESP32 development boards, more than a thousand branding projects, a studio, and an education arm that has trained tens of thousands of students — and they assume there must be a large building somewhere with a floor for each of those things.

There isn't. Team Incrix is 15 people in Kovilpatti, Tamil Nadu. We call ourselves the Mavericks. This article is a look at how that team is put together, which disciplines sit next to each other, and why we think a small team that spans software, hardware and design can build things a larger, more siloed team would struggle to.

Who is on Team Incrix

The easiest way to understand a small team is to look at the roles. Here is Team Incrix as it stands today, grouped by discipline.

Read down the right-hand column and a pattern shows up: a lot of the rows have an "and" in them. That is not an accident of a small headcount. It is the way we have chosen to work.

Disciplines, not departments

In a larger company, the embedded team, the software team, the design team and the sales team often live in separate reporting lines. Work moves between them through tickets and meetings, and each hand-off loses a little context.

With 15 people, we don't have the luxury — or the need — for that. Instead of departments, we think in disciplines, and we let people carry work across the boundaries.

Builders who also sell

Two of the clearest examples are on the build side. Jegannath and Janakiram are our embedded architects — they work on firmware, PCB design and the boards we ship under Incrix Automation. They are also responsible for course sales on the hardware education side.

That sounds unusual until you think about who a student or a college actually wants to talk to before signing up for an embedded systems course: the people who design the boards. The same logic applies to Kannan P, who builds AI backend services and also sells Classory. When the person explaining the product understands how it works underneath, the conversation gets honest very quickly.

Designers who think in systems

On the brand side, Johnson leads brand design, with Genga Parameshwari and Jon Mukesh on graphic design. Abishek, as C.I.O and Product Designer, sits between the product and the interface. Design at Incrix isn't a finishing step; it runs through software interfaces, hardware packaging, course material and client identities alike. We go deeper on how those hand-offs work in designers, developers and engineers building together.

Storytellers who ship every day

Arshad runs the content pipeline and campaigns and edits; Muthu Kumaresa and Kannan SK edit, with Kannan SK also shaping content strategy; Vignesh writes. Together they power our Studio and the content our community channels depend on.

The people who keep it running

Aravindh drives sales and marketing, Sheirly Twinkle handles administration and accounts, and Avinash leads the company as Director & CEO. In a small team these roles are not "support" — they are what make it possible for everyone else to keep building.

How a small startup team builds products across streams

A reasonable question at this point: how does a technology startup team this size actually get software, hardware and brand work done at the same time without collapsing into chaos?

We don't have a secret framework. What we have are a few plain habits that suit a small team:

1. Own the work end to endWhoever takes something on is expected to see it through — from understanding the problem to shipping it — rather than passing it along at the first boundary.
2. Share the toolsDesign lives in Figma, code lives in shared repositories with automated pipelines, and everyone can see the work in progress. Fewer private silos means fewer surprises.
3. Review across disciplinesA board, a screen or a brand system gets looked at by people outside the discipline that made it. The questions they ask are often the most useful ones.
4. Ship, then improveWe would rather put a working version in front of real users and improve it than polish something nobody has touched.

None of this is novel. Plenty of good writing exists on how teams work well together — the Atlassian Team Playbook is a practical collection of exercises for exactly this, and Harvard Business Review has covered team design for decades. The difference for us is less about method and more about proximity: when the whole product development team fits under one roof, collaboration is the default rather than a process you have to schedule.

What 15 people can build

It helps to see the output alongside the headcount. These are the things this team is responsible for today:

• Software — client applications built on cost-effective, maintenance-friendly serverless architecture, and our own SaaS product, Classory's multi-tenant LMS.
• Automation (hardware) — edge-native boards engineered in India, including Horizon Gen 1, Twinedge Dev V2, Horizon Dev-2 C6 and the Hexon Atom C6, plus education kits.
• Branding — 1000+ projects delivered, with a 4.9/5 rating.
• Education — Incrix University: 50K+ students trained, 50+ courses, 10+ partner institutions.
• Studio — photography, videography, ad films, brand films, social content and post-production.

We are not listing these to impress anyone. We are listing them because they explain the team structure. You cannot run five streams with 15 people unless people are willing to work across edges.

Three community channels, run by the team

One more thing surprises people: the team runs its own public channels, and they are not side projects.

Combined, that is more than 120K people. For a startup team in India working out of Kovilpatti, those channels matter: they are how students find our courses, how clients find our designers, and how engineers find our boards. They are also a quiet accountability mechanism. When you teach in public, you had better understand what you are teaching.

What this says about startup team culture

A small team spanning this much ground only works if the culture supports it. For us that comes back to the values we hold as a company: equity in mind, dignity in action, and quality solutions delivered in a reasonable way. We wrote more about that in why we don't want a typical startup culture.

If you want the longer story of how the team came together — from a town most tech maps skip to a company recognised by Startup India and DPIIT — read from Kovilpatti to building a technology company. And if you want to see how all of this adds up, our pillar piece, what are we actually building at Incrix, pulls every stream together.

The short version

Team Incrix is 15 people who would rather overlap than silo. Engineers who teach, developers who sell, designers who think in systems, editors who run pipelines, and an operations core that keeps it all standing. It is not the only way to build a technology company — but for a small team trying to make ideas alive across software, hardware and design, it is the way that works for us. If it sounds like your kind of team, keep an eye on careers at Incrix.