Do I have to define fields and pipelines before I can use anything?

Why tools ask for your fields first

No. You can start with the work in front of you and add fields later, only when you miss one.

You open a customer tool one morning. The screen is empty, apart from a list of fields waiting to be named. It asks you to decide what matters before you have any work to look at. You invent labels that sound professional, and you guess the order of the stages.

That guess rarely survives contact with real work. Your clients do not move in the order you predicted. The stage you called “Qualified” means nothing once a real job sits in it.

So you tidy the fields, then you reorganise the stages, and the tool still does not match the way you work. Every change sends you back through menus. Eventually you close the tab and reach for the notebook, where the list you kept still holds the truth about your jobs.

What you actually need on day one

Think about a single piece of work that is with you now. A job for a client, a request you have to answer, an order to get out. What you need to know about it is simple: what it is, who it belongs to, where it stands, and what happens next.

Say you design websites. A new project needs a name, a client, a stage and a next step. It does not need a budget field, a source field and three custom dates on the first morning. If you later find yourself writing the same detail in every note, that detail has earned a place of its own.

Say you are a plumber instead. A job needs the address, the customer, whether the quote is sent, and the next visit.

That is enough to run a day. The stages are the steps you already move work through, in the order you already use them. You do not need a field for everything you might one day write down. You need a place to record the thing in front of you and a way to see which stage it has reached.

The extra fields can wait. You will know exactly when you miss one, because a job will arrive and you will have nowhere to put a detail that matters. That is the moment to add a field. It is not the moment you start.

Start from what happened

You do not set anything up first. The sentence you type is what produces the note, the promise with its date and the next step, so no field has to exist beforehand. After a conversation, you type one sentence about what happened. Felesh drafts a note, the promise with its date if you gave one, and the next step. Each draft shows its reason and waits for your yes.

Stages arrive in a template

Each area of your work arrives with a template board, so the stages are already in place and you have something to react to rather than a blank screen. You can add a stage from chat, and an area can hold several boards. The order you settle on is the order your work already moves in.

Your words, not its own

Categories, tags, reasons and priorities are written in your own words. If your studio says ‘waiting on client’ rather than ‘blocked’, the record says ‘waiting on client’, and anyone reading it a month later knows what you meant.

When a plain sheet is still enough

Be honest about your own size. If you carry a handful of jobs and every one of them sits in the same place until it is done, a plain sheet holds that list well. You do not need stages, because there are no stages to move through.

A customer tool earns its place when the work has more than one step, and when jobs wait at different points and you have to remember which is which. Until then, the sheet you already keep is the right tool. The moment to change is when you catch yourself keeping a second list to remember what the main list does not say. That second list is the stages you have not named yet.

Start with one part of your work

Pick one conversation from today and type one sentence about what happened. The rest can wait. See how setup works, and how pipelines fit in.