From client request to quote.

The app is the Task App starter, extended for a client: tasks, projects, a board view and an assignment action. Each task has one assignee.

1. The request

In a hand-built stack, the honest answer is “let me look into it”, followed by an hour of searching through the table, the migration, the DTOs, the API, the forms and the list views. Then you estimate from memory and add a margin for what you missed.

2. Change the model, not the layers

In logiCells, the relation between Task and its assignee is declared once, in the model. You change it there: the assignee becomes a list of assignees. You don’t touch views, actions or services yet.

3. Ask what it affects

Before applying anything, ask the incremental planner what the change touches.

$ cell application compile plan app.lgc

  change    Task.assignee → assignees (one → many)
  affects   view TaskBoard
            view TaskDetail
            action AssignTask
            service contract /tasks
  data      1 relation migration
  plan      incremental, safe to apply

You now have the full list of what the request touches, and whether it can be applied incrementally or needs a wider rebuild.

4. Turn the plan into a quote

Every affected structure becomes a line you can explain to the client. The quote comes from the plan, not from your memory of the codebase.

Send it with the plan attached. A client who can see why a change costs what it costs argues less about the price.

5. Apply and run

Once the client agrees, apply the change and run the application.

$ cell server start app.lgc

6. What you keep

The change lives in the model, where the next developer, or you in six months, can read it. If several of your clients need multi-person assignment, the pattern is reusable on the next mission.