Walkthrough · No. 05

Internal CRM and task tools: Focused operations software for a lean team

Why Factly built its own CRM and task tools instead of adopting a suite, and how enquiries flow to proposals, projects and tasks.

  1. Before: Enquiries in personal inboxes
    After: One record per organisation, with history
  2. Before: Proposals in shared documents
    After: Proposals linked to the record and the pipeline
  3. Before: Projects in a spreadsheet
    After: Accepted proposals become projects with tasks
  4. Before: Tasks assigned in chat
    After: Tasks linked to projects, owners and dates
  5. Before: Weekly report compiled by hand
    After: Pipeline and delivery views that build themselves
Fig. 1 Before and after: the workflow pattern. Screenshots on request. Internal tool

§ 01 Problem

The problem

A small team runs several products and a data journalism desk. Enquiries, proposals, projects and tasks lived in inboxes, spreadsheets and chat; suites meant configuration, licences and a vendor’s process.

§ 02 Information and data

What made it hard

  1. The same organisation as a lead, a subscriber and a partner, with no single record.

  2. Proposals and projects that reference each other but live in different tools.

  3. Tasks assigned in chat with no link to their project.

§ 03 Workflow and design

The decisions that shaped it

  • D1

    Model the real pipeline

    Stages, fields and views mirror how an enquiry actually becomes a subscription or a project.

  • D2

    Proposals flow into projects, projects into tasks

    An accepted proposal carries its scope and milestones into the project it creates; tasks link back.

  • D3

    Workflow first, AI second

    Well-made software first; assistive features where they help, with a review step.

§ 04 Shipped, not planned

What it actually does

  • Organisation and contact records with a complete history
  • Proposals that carry scope and milestones into projects
  • Projects with tasks, owners, deadlines and documents

§ 05 Input → steps → output

Walkthrough

The records are real, so the steps describe the workflow without screenshots.

  1. Input

    An enquiry, by email or web form.

  2. Step 1: Capture

    The enquiry becomes a record on the organisation: contact, ask, next step.

  3. Step 2: Propose

    A proposal is drafted against the record and tracked on the pipeline.

  4. Step 3: Deliver

    An accepted proposal becomes a project with tasks, owners and dates.

  5. Step 4: See the whole

    Pipeline, workload and overdue items in views that build themselves.

  6. Output

    One record of each relationship and project, and reporting nobody has to assemble.

§ 06 Evaluation

How we check it

  • The team uses them every day instead of the spreadsheets they replaced.

§ 07 Evidence

The figures

No figures are published for this tool.

§ 08 Limitations and lessons

Limitations and lessons

read this part first

Limitations

  • Built for Factly’s own needs; client tools are built to the client’s process.
  • The records are real, so no screenshots are published. We walk clients through on a call.

Lessons from operation

  1. Building to actual needs is cheaper than configuring a suite to approximate them.
  2. The chain from enquiry to task is the product; the value is that the pieces link.
  3. Add AI after the workflow is in daily use.

Sources (1)

  1. [1] Factly on GitHub · github.com (opens external site)

Sources reviewed 15 November 2026.

Discuss a project

Running your operations in spreadsheets and chat?

Tell us how an enquiry becomes a project today.