Roles and costs

Register roles with cost-per-hour (how much it costs you) and price-per-hour (how much you charge). The Studio uses this table to estimate the viability and margin of initiatives.

It is the table that says how much an hour is worth for each role on the team. It feeds the cost of hours logged on requests, the margin per project, the suggested price on the proposal and the profitability simulation. There are two columns per row and it takes ten minutes; without it, everything that depends on hourly cost shows zero or guesses a single value for everyone.

Cost/hour = what that hour costs the company: salary plus payroll charges and benefits, divided by the working hours in the month (≈160). A CLT employee on R$ 8,000 with 70% charges costs ≈ R$ 85/h, not R$ 50/h — this is the most common mistake here, and it inflates the margin of every project at once. Price/hour = the list price you charge the customer for that role. The difference between the two is the gross margin of the hour sold.

The adjustment applies to calculations from now on. Hours already logged and closings already done keep the value that applied on that day — that is what keeps the month-to-month comparison honest. If you need to reprocess a month with the new value, that is a conscious decision and goes through the closing of that period, not through this screen.

When you save a view with the Views button, it stores four things: the search text, the applied filters, which columns appear (and in what order) and which column the list is sorted by. Applying the view restores everything at once — including resetting the sort and the page you were on, so the result is exactly what the view describes. Views saved before this version remain valid: whatever they didn't store simply doesn't change when applied.

Nas fichas, sair de um campo já dispara a conferência do que dá para conferir na hora: campo obrigatório deixado em branco e e-mail mal formado. O aviso aparece embaixo do campo e desaparece quando você começa a corrigir. Campo numérico não precisa de aviso: ele simplesmente não aceita letra enquanto você digita. Isso é conforto, não a validação final: ao salvar, o sistema confere tudo de novo do lado do servidor.

They go in with a price/hour of zero and a filled-in cost/hour. This is deliberate: they show up in the cost of operations without inflating forecast billing. Leaving the price blank or repeating the cost would make the platform imagine revenue that does not exist.

Open the record and look at the Timeline on the right: it shows each change as "from one value to another", with the person and the date. When there are many changes, use the two filters at the top of the timeline — one by field, the other by person. The search runs in the database, so old changes show up just the same. You can also ask Tenkai: "who changed contract 482?".