Insightly

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build the CRM-and-delivery system I actually need instead of Insightly.

The idea worth copying is the join: **the deal and the work that follows it are the same record.** Most companies run a CRM and a project tool that know nothing about each other, and every handover is a person re-typing what was already agreed.

Be realistic about scope, though — this is two products, and building both badly is worse than buying one.

STACK
- Node 20+ with Fastify, server-rendered HTML with a little vanilla JS
- SQLite through better-sqlite3, WAL mode, FTS5 across everything
- Caddy in front

THE DATA MODEL
- companies, people, deals as in any CRM, with an append-only stage history
- projects: id, deal_id, name, starts_on, due_on, owner_id, status
- tasks: id, project_id, title, assignee_id, due_on, status, position
- templates: id, name, tasks_json — the delivery checklist for a kind of work
- **projects.deal_id is the whole architecture**: what was sold is one query away from what is being delivered

THE HANDOVER, WHICH IS THE POINT
- Winning a deal creates a project from a template chosen by deal type, carrying across the company, the contacts, the value and every note
- **Nothing is re-typed, and nothing is lost.** The delivery team reads what was actually promised rather than what the salesperson remembers
- The project links back, so 'what did we sell them' is answerable during delivery and 'how did delivery go' is answerable before the renewal

WHAT THIS MAKES POSSIBLE
- Margin per deal: sold value against tracked delivery time at cost rates. **Most companies cannot answer this, and it is the question that decides which work to take more of**
- Delivery slippage by deal type, which tells sales what to stop promising
- A renewal list built from projects finishing, not from a date somebody typed

KEEP THE HALVES SMALL
- CRM: companies, people, deals, activities, a next action on every open deal, a required lost reason
- Delivery: projects, tasks, four statuses, a due date, a template. **No Gantt, no dependencies, no resource planning** unless somebody asks twice
- One search across both, which removes the need for most navigation

WHAT NOT TO DO
- Do not build relationship mapping. It demonstrates well and is used by nobody
- Do not let delivery tasks into the pipeline reporting. Two things called 'open' that mean different things is how dashboards become useless

WHAT MATTERS MOST
The deal-to-project link and margin per deal. The first removes the handover; the second answers a question most companies are guessing at.