Pricing Based on Subject, Scope and the Support You Need
A single debugging issue is scoped differently from a multi-part software project. Send the brief, deadline and your current work so the required support can be assessed clearly.
What affects the price?
The main factors are technical difficulty, number of files, existing progress, depth of explanation or review, testing effort and deadline.
How to get a useful scope estimate
Send the assignment brief and explain what you have already completed. For code problems, relevant files and the exact error message help. For reports or projects, include the outline, marking criteria and required submission files.
Send your assignmentOne error message is not the same scope as a multi-week software project
A small debugging request may involve one function, a stack trace and a few tests. A project may also include architecture, multiple files, Git, testing, documentation and presentation requirements. A useful price therefore depends on knowing the real scope.
If your deadline is close, mention it at the beginning. It is equally important to say whether you already have an approach or are still trying to understand the brief.
Send four things
1. The assignment brief or screenshot. 2. Deadline. 3. Your current progress. 4. A short description of the problem or support you need.