KatsaSend the job

Working rules

A written first milestone, before access.

The fastest safe start is one useful job with a visible finish. We ask only for details that change the scope, price, timing, or access plan.

Send the job
Digital tools arranged on a work surface

Jobs that belong here

  • Send the current URL, file, screenshot, recording, or rough message
  • Read the finish, price, timing, access, checks, and exclusions
  • Approve the milestone before account access or work begins
  • Review the result, test record, files, notes, and handoff

What comes back

  • One accountable project lead
  • Client-controlled accounts wherever the tools allow it
  • No scope expansion without written approval
  • Specialist access disclosed before private material is shared

A request may end with a clear no-fit answer. That is better than a vague sale.

Questions before access

Useful answers, before the job starts.

Do I need a formal brief?

No. A URL, screenshot, file, or rough explanation is enough for the first review. We ask follow-up questions only when the answers change the job.

When do I receive the price?

Before the milestone begins. The scope gives either a fixed price or an hour cap and states what would require a separate approval.

Who owns the finished work?

The scope and invoice state the ownership terms. Client accounts and supplied files stay under client control, and the handoff lists what comes back.

Send the current state and the finish you need.

A URL, file, screenshot, or rough message is enough for the first review.

Send the job