Contact / Intake

A useful first conversation starts with context.

CAERUS uses the first request to identify the business problem, user impact, constraint and next decision before work becomes a project.

Intake questions

Send enough context to make the next step clear.

The first response should be able to classify the request as ready, discovery needed or at risk.

Some required context is missing. Complete the marked fields before sending.
The request could not be sent. Try again or use the email fallback.
Email CAERUS

Describe the business problem, not only the requested task.

Name the users, teams, clients or workflows that feel the problem.

Mention websites, systems, content, processes or dependencies already in place.

List technical, stakeholder, timing or operational constraints.

Clarify who can approve scope, criteria and next steps.

Define what should be true when the work is complete.

Submit context

Send context for review.

CAERUS reviews the request before scoping.

After submission

What happens after you send context.

CAERUS reviews the intake before scoping. The first reply should create a decision path, not a premature project promise.

Process

01CAERUS receives the intake context
02The request is reviewed before scoping
03You receive a next decision path

First response can be

Ready

A scoped call can be proposed.

Discovery needed

More context is needed before scope.

At risk

Owner, criteria or feasibility are unclear.