How to use Costdown

Costdown is where you record a cost-reduction improvement as numbers, then compare it against other factories in the same country. The first two sections walk you through doing exactly that, start to finish. The rest explain things you cannot work out by looking at the screen — read them when you need them, not before you start. Each input field also has its own explanation in place: see The ? beside each field.

Where to start

It depends on what you came here to do. Three ways in, in no particular order:

The Calculator and the Write page share the same formulas, so a figure you try out in the Calculator comes out the same when you turn it into a proposal.

Writing a proposal, start to finish

This follows the actual order of the fields on the Write page. Before you open it, five things are worth having in hand — you can write without any of them, but the proposal then sits at a low trust level:

• The cost BEFORE and the cost AFTER, broken down by category — not a single total.
• How you measured those two figures: hand counts, shift logs, production reports, invoices.
• Monthly volume, working days, shifts per day, hours per shift — the system needs them to bring costs down to a single part.
• The money already invested, if any. If none, tick "This proposal needs no investment".
• Machine names, material codes, specific models — the more specific, the more a reader can match it against their own shop floor.

About the Before and After columns: Before is the current state, After is once the improvement is in place. If a category is untouched by the improvement, leave BOTH columns blank — do not copy the Before figure into After to fill the gap, because that states a category the improvement has nothing to do with.

The panel titled "What the system reads from your figures" sits in the right-hand column and runs while you type, not after you save. It points out things that are hard to notice yourself: a row contributing almost nothing, a category wildly out of line with the rest, a place where you filled one side and left the other blank. Reading it while typing is worth far more than reading it after forty rows are already in.

If you are not ready to publish anything, use Intelligence → Calculator: same formulas, no account needed, nothing stored. Try figures there first and move to Write later if you want.

The ten cost categories

Costs are split into ten categories. You do not have to fill in all ten — only the ones your improvement actually touches.

Blank does not mean zero

This is the easiest thing to get wrong, and getting it wrong produces a wrong cost figure that looks exactly like a right one.

A blank field means you have NOT STATED it, not that you are asserting the category is zero. The system distinguishes the two states and displays them differently. If you genuinely mean "this costs nothing", type 0 — that is an assertion, and it is not the same as leaving the field empty.

The reason: a proposal with half its categories blank still produces a very attractive savings figure. If blank counted as zero, nobody could tell "this improvement really saves a lot" apart from "the author has only filled in half of it".

Hard cash or cost avoidance

These two kinds of saving look identical on paper but behave differently in the accounts, so every proposal should say which one it is.

• Hard cash: after the improvement, the amount actually paid each month goes down compared with what is being paid today. You pay 50 million for electricity, replace the motor, and it becomes 42 million — next month's bill is 8 million lower.
• Cost avoidance: the amount paid does not go down; it simply fails to rise the way it would have. The supplier announces an increase from 50 to 55 million, you renegotiate and change material to hold it at 50 million — the bill is still 50 million, and accounting sees nothing go down.

If you are not sure, leave it blank. Blank means "not stated"; guessing means stating something false, and a reader who knows the trade will notice.

The four trust levels

Every proposal carries a trust level. The system RECALCULATES it from the evidence actually present — it is not a label you pick, and writing at greater length does not raise it.

The "How it was verified" field is the most important one when writing a proposal. Something vague like "we observed a clear reduction" leaves the proposal at the lowest level and out of the ranking, no matter how good the numbers are. Something specific — what was measured, with what, against what, who signed it off — raises the level.

The number of posts never counts towards ranking, not even as a tiebreaker. Posting more does not place you higher.

Comparing against other factories

Ranking and comparison happen WITHIN A SINGLE COUNTRY only. An improvement saving 20% in Vietnam and one saving 20% in Germany cannot be compared directly: labour, power and material prices are too far apart.

For that reason comparisons are measured in percentages and in months to payback, never in absolute money. The exchange rate is taken for real at the moment of saving and then frozen, so an old proposal does not change meaning when rates move.

Grouping with colleagues

Colleagues from the same company are grouped by a random join code, not by naming the employer. You create a code, hand it to a colleague, and whoever enters it joins the same group — which lets you share internal material codes and pool figures without saying where you work.

The code is shown ONCE at creation and is never stored in readable form. If you lose it, nobody can retrieve it, administrators included — create a new one and revoke the old.

When someone applies your improvement

A proposal can go on to become a project with two sides: the one who offered the improvement and the one who applied it. The side that applied it submits the real figures afterwards, and the other reviews and confirms them. Only when both agree is the result recorded as verified.

That is the thing a spreadsheet cannot give you: a number that someone else, at another factory, has put their name to as well.

The ? beside each field

Almost every input field has a ? beside it. It opens that field's own explanation, and each one answers four questions: what it is, when to fill it in and when not to, an example with real numbers, and what other situations the field covers beyond its own name.

The fourth is the one worth reading. A field name is the shortest name, not the fullest one — seeing "Weight (kg)" and assuming it is only for metal means skipping the whole material category when you work in plastics, textiles or wood.

Where a field has a formula, the explanation gives the formula and its source.

Why not just use Excel

That is a fair question, because Excel is faster to type into, freer in layout, and works offline. Costdown does not try to win on any of those three.

There are five things a spreadsheet cannot do, and they are the entire reason Costdown exists:

• Share one library of materials, machines and processes — instead of everyone typing their own spelling of the same thing and then being unable to add the numbers up.
• See figures from other factories in the same industry and the same country.
• Let a counterpart who actually applied your improvement confirm the real number themselves.
• Keep an edit history that cannot be deleted: change a savings figure and the system records the old value, the new value, which account changed it, and when.
• One single formula for everyone — no two spreadsheets producing two answers and an argument about which one is right.

If the work in front of you needs none of those five, Excel really is faster, and we would rather say so plainly.

When something does not match

If anything in the product behaves differently from what this page describes, that is our mistake and not yours — please tell us through the 문의하기. Messages are stored and given a case number immediately, so your request does not disappear.