KASTRICK / PROJECT REQUEST
Bring the problem. We can shape the brief.
You do not need a finished specification. Give Kastrick the useful context—what you want to achieve, what already exists, constraints and references—then review the brief before it is sent.
01 / CONTEXT
Start with the real problem
A goal and constraints are more useful than pretending every implementation detail is already decided.
02 / SCOPE
Kastrick reviews the shape
The request is context for scoping—not an automatic purchase or a promise that every requested feature is already defined.
03 / RELATIONSHIP
One-off or ongoing can both fit
Use the form to say whether this is a single delivery, continued maintenance or longer-term engineering work.
References help, but they are not required to be perfect. A rough example plus a clear explanation of what you like or dislike is usually more useful than a vague request to ‘make it modern’.