Software product

KPS

A system for running work with the rules built in.

KPS stands for keinekratzer Production System. It puts the management rules I use in client work into software.

Your team learns the process while doing the job. The checks are already there; you add your people and company rules.

If a client changes the scope, KPS checks what else needs to change before the work moves on.

Help choose what KPS handles first and request a free invitation to try the first version on your own work.

KPS change request interface showing a proposed scope, time and price change
Example

A client asks for a change

A small client request can affect more than the task it came from. KPS checks that before anyone agrees to the change.

Known
Current agreement: one language

The current agreement stays attached to the job. The team can open the agreed version from the job.

New request
The client asks for a second language

KPS treats it as a change to the existing job.

KPS checks
Affected deliverables Existing pricing rule Deadline dependency Who may approve the change Whether a commercial decision is missing
Human decision
The responsible person agrees the change

A person approves the change. KPS records the decision.

Current work changes
The people doing the work get the updated instruction

The agreed change reaches the people doing the work. The new requirement reaches the task, its files and the approval check.

Next similar request
Check the language before production starts

The team adds a language check to the next brief. The person doing the job sees the question at the right moment.

Built-in method

What KPS already knows

A handoff needs the current instructions. A finished deliverable may still need approval. These checks are part of the process from the start.

The next person gets the current instructions

The client changed the requirement yesterday. The next person gets the new version today.

Finished and accepted are separate

Work can be finished before the client approves it. KPS keeps those states separate.

A change reaches the rest of the job

A second language adds another deliverable. KPS checks the price and date, then carries the agreed change into the related tasks and approvals.

The right person approves the exception

A request falls outside the normal limit. KPS sends it to the person with authority to approve it.

The next job uses what your team learned

Approve a better instruction or remove a check you no longer need. The next similar job uses the updated process.

Your company

Start with work your team already does

Try a handoff or a client approval. You can extend the setup as you use it.

1

Choose the work

Use a handoff or client change your team already needs to handle.

2

Add your company

Add who owns the work, who may approve it, what you promised and where the current information lives.

3

Improve the next job

Approve a better way to handle the work. The next similar job uses the updated instructions.

Where it comes from

Built from real client work

A client approved a change in chat, but the task still had the old instructions. Someone finished their part, but the client had yet to accept it. I kept having to put these rules into the tools teams used.

I was already handling that with the same rules. I started turning those rules into KPS.

KPS

What would you use KPS for?

Tell me what you’d use KPS for. Your answers help me choose what goes into the first version. Leave your email to get an invitation to try it for free on your own work.

Want help with your team’s work now? See operations services and prices →