Kunj Patel
Book a call
Portfolio / v4
Available for new work

Considered interfaces,
resilient systems.

I'm Kunj Patel — a software developer specialising in ERPNext / Frappe and full-stack web. Currently at Samarth Diamond, shipping production ERP for diamond & jewellery manufacturing. Open to select freelance work and full-time roles.

1.4+
Years in production
5,000+
Users served
70%
Faster analytics
99.9%
Delivered on time
scroll
ERPNext
Frappe
TypeScript
Next.js
React
PostgreSQL
ClickHouse
FastAPI
Python
Node.js
ERPNext
Frappe
TypeScript
Next.js
React
PostgreSQL
ClickHouse
FastAPI
Python
Node.js
01

About

The short version

I build software that respects the operator — whether the operator is a floor supervisor tracking a diamond between cutting and polishing, an analyst drilling into a pivot, or the next engineer who opens the file.

My specialty is ERPNext & Frappe — customising doctypes, workflows, and reporting for manufacturing businesses where spreadsheets stopped scaling. Around that core, I work full-stack: React / Next.js on the front, FastAPI or Node on the back, Postgres or ClickHouse underneath.

Day job: software developer at Samarth Diamond, shipping production ERP for diamond & jewellery workflows. Nights and weekends I take on select freelance work and write about the craft.

Stack

ERP
ERPNextFrappeCustom doctypesWorkflows
Frontend
ReactNext.jsReact NativeTypeScriptTailwindCSS
Backend
PythonFastAPINode.jsExpressREST APIs
Data
PostgreSQLClickHouseMariaDBMySQLMongoDB
Reporting
FlexMonsterPivot analyticsClickHouse pipelines
Tools
GitRBAC/AuthAgileVercel

Currently

  • Software Developer · Samarth DiamondNov 2024 →
  • B.Tech, Computer Engineering · Sankalchand Patel CoE2021–25
  • Based in Mahesana, GujaratIST (UTC+5:30)
02

Selected work

Case studies · 2022 — 2025
  • J
    Samarth Diamond
    ERPNext developer

    Problem

    Diamond and jewellery manufacturing lives in spreadsheets, paper challans, and WhatsApp messages. Pieces change hands a dozen times between rough stone and finished SKU, and the business loses time, traceability, and weight reconciliation at every handoff. The goal is one system that the floor actually uses — not another tool they route around.

    What's built & what's next

    1. ShippedMapped the physical workflow — issue, cut, polish, certification, setting, return — with the operations team before modelling any doctype.
    2. ShippedShipped the first module: basic diamond issue / return against a production bag, so every piece that leaves a department has an auditable record.
    3. BuildingBuilding custom Frappe doctypes for multi-stage production tracking — priority flags, department-level routing, and re-issue handling.
    4. BuildingAdding jewellery production workflows on top: BOM, stage transitions, and rework loops that match how the floor actually operates.
    5. BuildingPlanning analytics and reporting modules so supervisors see live bottlenecks instead of end-of-day summaries.
    6. BuildingPlanning a compliance trail: every hand-off gets an auditable record without anyone having to remember to log it.

    Where it's heading

    The issue / return module is live on the floor and already replacing paper challans for that step. Next milestone is full production-stage tracking; after that, analytics. Success will be measured by how much of the daily operation the team chooses to do inside the ERP rather than around it.

    ERPNextFrappePythonREST APIsMariaDB
    Full case study
More on GitHub — public and private projects alike.github.com/hyphen04
03

Services

How we can work together
01Service

ERPNext & Frappe

Custom ERP modules, doctypes, and workflows for manufacturing, inventory, and production businesses. End-to-end ownership from discovery to rollout.

  • Custom doctypes
  • Workflow automation
  • REST API layer
  • Reporting & analytics
02Service

Full-stack web

React/Next.js front-ends backed by Node, Python, or Frappe APIs. Dashboards, portals, internal tools — shipped with CI, previews, and real analytics.

  • Design system
  • Typed API
  • Role-based auth
  • CI + previews
03Service

Reporting & analytics

When your dashboard is too slow to explore, I rebuild the layer underneath. FastAPI + ClickHouse pipelines, FlexMonster integrations, query tuning.

  • Pipeline design
  • ClickHouse schema
  • Sub-second pivots
  • Ops runbook

How I work

01

Scope

Thirty-minute call, a one-page brief, a quote. No billable hours until we both agree what we're building.

02

Build

Short cycles, shared previews, weekly demos. You see the product grow — no three-week silences.

03

Ship & iterate

Deploy, observe, adjust. I stay on for a 30-day window to fix what the real world finds.

04

Working together

The questions people usually ask

Before you write, here’s what I’d tell you on the call.

If something below isn’t covered, ask it directly in an email. Fastest way to get a useful answer is to lead with what you’re trying to build and why.

  • A thirty-minute scoping call, a one-page brief, and a quote — all free. If we agree, I work in short cycles with weekly demos so you always see the product grow. Most projects land in a 2–6 week window.

05

Writing

Notes on the craft
06 / ContactGujarat · IST

Let’s build something that matters.

The fastest way to reach me is email. Tell me what you’re building, who it’s for, and roughly when you need it. I reply within one business day — or not at all if it’s a cold pitch.

Book a 30-min call
Kunj Patel.