R&D and product studioIndiaA division of SETITUP

We study how businesses run, then build the software they lack.

The research and product studio inside SETITUP. We find the problems businesses live with, then build around them.

01Method

From observation to product

Five stages, in order. A product only moves forward when the stage before it holds.

  1. 01

    Observe

    Find the problems that keep recurring across real businesses.

  2. 02

    Research

    Learn the workflow, the people in it, the market and the economics.

  3. 03

    Validate

    Test the assumptions against real users and measurable evidence.

  4. 04

    Build

    Develop prototypes, then production software.

  5. 05

    Scale

    Turn what works into a product a business can rely on.

02Position

Most software gets built to a brief. We build to evidence.

We start with the problem, not the request

  • Stockrooms
  • Sales desks
  • Back offices

SETITUP LABS is where SETITUP experiments with products. We spend our time in stockrooms, at sales desks and in back offices. Rather than waiting to be told what to build, we study how businesses operate, look for the problems that keep coming back, investigate whether anyone has solved them properly, and build around the opportunities that survive that scrutiny.

Business research, product thinking, design and engineering all sit in the same room, which is why a finding can become a prototype without being handed across a wall first.

03Territories

Where we are looking right now

These are research territories, not a service list. Each is an area where we are actively studying how small and medium businesses work today.

  • Finance operations

    Payments, expenses, invoices, reporting and operational visibility. Why MSMEs wait to get paid
  • Workforce

    Employees, tasks, schedules, productivity and internal coordination.
  • Industry software

    Vertical software for markets that larger vendors have skipped.

04Toolkit

What we build with

A working set, not a commitment. What a product needs is decided after the problem is understood.

  • Web
    • Next.js
    • TypeScript
    • React
    • Tailwind CSS
  • Backend and data
    • Node.js
    • Python
    • PostgreSQL
    • Redis
  • Infrastructure
    • Cloudflare
    • Docker
    • CI/CD
  • AI and ML
    • LLM APIs
    • RAG
    • Vector search

We do not start with a technology and look for somewhere to apply it.

The stack is chosen per validated problem, and replaced when the problem calls for something else.

05Origin

Built inside SETITUP

SETITUP LABS operates as the research and product division of SETITUP, which builds custom technology systems for businesses and works close to how they actually operate.

That work is where our problems come from. Every engagement surfaces friction someone has learned to live with, and some of it is worth turning into a product.

Visit SETITUP
  1. 01SETITUP
  2. 02Real businesses
  3. 03Real problems
  4. 04SETITUP LABS
  5. 05Research and validation
  6. 06Products

06Product

The first product out of the lab

SETITUP Inventory keeps stock and the books in one system. It is in development: the core is built and tested, and it is not yet generally available.

  • Stock
    • Multiple locations
    • Free to sell, not just on hand
    • Transfers with goods in transit
    • Reorder ranked by cover
  • Purchasing
    • Quotes, orders and bills
    • Part deliveries
    • Payments against bills
    • Suppliers and what is owed
  • Sales
    • Quotes and orders
    • Stock reserved on confirm
    • Part shipment
    • Customers and open orders
  • The books
    • Double-entry ledger
    • Trial balance
    • Profit and loss, balance sheet
    • Period close

Every stock movement writes its accounting entry in the same transaction.

That is the idea the product is built around. The shelf and the books cannot drift apart, because neither is written without the other.

What SETITUP Inventory does

07Notes

Inside the lab

What we write down while studying how businesses run: where the workflow breaks, and what that implies for the software.

All research notes

08Contact

Have a problem worth investigating?

If you run a business and there is a workflow you know could work better, we want to understand it. Tell us what breaks, how often, and what it costs you when it does.

Your operational problem could become the starting point for the next product we build.