KLYKX · Getting started

Your app, made yours.

No code. Every KLYKX app is built from a few simple pieces — and you shape them just by describing what you want. Here's where to start, and what each piece actually does.

Describe it → KLYKX builds it → You customize → Go live
Start here

Three steps from idea to running app

You'll spend most of your time in step 2 — and the assistant does the heavy lifting.

1

Create your app

Describe it in a sentence and KLYKX designs and builds it — or start from a ready-made template and clone it in one click.

My Apps · Templates
2

Customize it

Open the assistant (bottom-right) and just ask or instruct: “add a Priority field”, “who approves a leave?”, “email the manager when it’s submitted.” It explains, then builds.

AI Assistant
3

Go live

Add your real people and their roles, clear the demo data so you start clean, and you’re running the app for real.

Users · Test Data
The building blocks

Four pieces do most of the work

Learn these and you can build almost anything. Everything else plugs into them.

Entity Entities · Masters

Your data. A thing your business tracks — a Customer, an Invoice, a Leave Request. Its fields hold the details: name, date, amount, status. Everything else in the app hangs off entities.

e.g. add a Priority field to Complaints, or a new Vendor master.

Page Pages

Where people work. Every entity gets a page — a form to fill in and views to browse: a list, cards, a kanban board, a calendar. This is what your team actually sees and clicks.

e.g. show Orders as a kanban board, or add a self-service “My Requests” page.

Workflow WorkFlows

The approval path. The stages a record moves through — Draft → Submitted → Approved → Paid — with the buttons each role can press and a status bar on every record.

e.g. route a leave to the manager, then HR, before it’s approved.

Bizflow Biz Flows

The automation. The logic that runs for you — total an invoice, calculate leave days, post a ledger entry, or call another system. Runs on a save, a status change, or a schedule.

e.g. auto-total line items, or calculate worked hours from check-in/out.

Six more building blocks

These plug straight into your data and flows

Same idea as the core four — describe what you want and the assistant wires it up.

Scheduler

Time-based jobs. Run a bizflow on a schedule — monthly payroll, weekly preventive-maintenance work orders, daily reminders.

e.g. run payroll on the 1st of every month.

Scheduler

Data trigger

“When this, do that.” Watches your records and fires an automation the moment a condition is met.

e.g. stock ≤ reorder level → raise a reorder.

Data Triggers

Documents

Branded PDFs. Invoices, receipts, certificates with a scannable QR code — generated automatically when a record hits a status.

e.g. an Invoice PDF when a Quotation is Accepted.

Documents

Notifications

Keep people posted. Email or WhatsApp messages sent automatically on key workflow actions.

e.g. email the manager when a leave is submitted.

Notifications

Integrations

Connect the outside world. Slack, Teams, Stripe, Razorpay, KYC, or any REST API. Paste a key, test it, and use it from a flow.

e.g. post to Slack, or create a payment link.

Integrations

Reports & dashboards

See how it's going. KPI cards and charts over your data, arranged onto a dashboard for each role.

e.g. revenue by month, orders as a KPI.

Reports · Dashboards

The shortcut

Not sure where to click? Just ask.

The assistant is on every page. Ask a question and it teaches you; give an instruction and it builds it — no menus to hunt through. It knows your app’s real entities, forms, and flows.

Before you launch

A quick go-live checklist

Add your people & roles

Real users, reporting lines, and who can do what.

Clear the demo data

One click removes the sample records so you start clean.

Run one end-to-end

Create a record and push it through its workflow once.

Connect your integrations

Paste your keys (Slack, payments, …) and test each one.

Create your first app — free