A customer asks for a small job. A few emails later, the job includes extra work, a revised deadline and a price you cannot find. AI can help organize that trail. It cannot decide what the customer agreed to or turn an unpaid invoice into income.
For a consultant, tutor or other small service business, a useful deal desk can be one simple record per job. The purpose is to connect the request, the approved work and the payment evidence. You do not need an automated investment engine or an expensive software stack to begin.
Start with one source of truth
Choose a spreadsheet or the business system you already use. Give each job an identifier. Record the customer reference, agreed deliverable, price, due date, payment terms, current stage and next action. Link to the original agreement and invoice in storage with appropriate access controls.
Separate confirmed facts from questions. A proposed date belongs in a proposal field until the customer accepts it. A remembered phone conversation needs a written confirmation; an AI summary of your recollection is not evidence of agreement.
A workable sequence is inquiry, quote sent, scope approved, work underway, delivered, invoiced and payment recorded. Add an on-hold or disputed state so difficult jobs do not disappear inside a tidy pipeline. One business may invoice before delivery or require a deposit; use stages that reflect its actual terms.
Use AI to extract details, then check them
Begin with one completed job whose outcome you know. Supply a redacted excerpt of the request and agreement. Remove personal addresses, account details and confidential client material that the task does not require. Confirm that your chosen service and business policies permit the remaining information to be processed.
Extract the agreed deliverable, price, deadline, included revisions and payment terms from these excerpts. For each field, point to the supporting sentence. Distinguish proposals from accepted terms. Mark anything missing or conflicting as unknown. Draft questions for me to review; do not send messages or change a record.
Compare every number and date with the originals. Check who accepted the terms and whether a later message superseded them. If the documents conflict, keep both references and resolve the disagreement yourself. The model should not quietly pick the more convenient version.
Keep changes separate from the original job
Consider a fictional editing project: $600 for one document and one revision. The customer later requests a second document. Record that request as a proposed change, with its additional price, delivery implications and acceptance status.
AI can draft a clear explanation of the proposed change. Review and agree on it with the customer before treating it as approved work. A draft quote is neither consent nor a reason to demand payment. If you decide to include the extra work without charge, record that decision too.
This small habit prevents an assistant from combining every request into a single supposedly agreed scope. It also helps you see why a job took longer than expected when you review your pricing later.
Distinguish an invoice from a payment
Your invoicing system should hold the official invoice record. For example, Stripe describes separate draft, open and paid invoice states. Finalizing a draft generally changes it to open; an unpaid invoice can remain open. These are different from your internal delivery stages.
A spreadsheet entry that says paid is not enough on its own. Reconcile it with the relevant payment or bank record, including partial payments, refunds and fees. Some systems allow staff to mark an invoice as paid outside the platform, so understand the evidence behind the status.
For illustration, a $600 invoice with a $200 deposit leaves $400 to collect, assuming no adjustments. AI can help present the arithmetic, but your records must establish that the deposit actually arrived. Revenue, cash received and profit are separate measures; use your accountant’s guidance for financial reporting.
Draft follow-ups without handing over control
Ask AI for a polite reminder based on the verified invoice number, outstanding amount and agreed due date. Read it before sending. A missing receipt, disputed delivery or agreed extension may make a generic overdue notice inappropriate.
Keep permissions narrow. A drafting assistant does not need permission to charge a card, alter bank details, apply a late fee or change payment terms. Treat an unexpected request to redirect a payment as something to verify through a known contact route, not an instruction to execute automatically.
Review the exceptions once a week
Look for work with no written approval, delivery with no invoice, open invoices with no next action and payment records that do not match. Ask the assistant to list missing fields and contradictions, then check the underlying documents. Avoid sending the entire customer database when a small redacted sample will answer the question.
After a month, compare the time spent maintaining the record with the confusion it prevented. A useful system makes the next action clearer and leaves a traceable history. Faster messages or a larger list of prospects do not demonstrate that the work is profitable or that customers have paid.
Reviewed September 28, 2026. Prepared with AI assistance and checked against the linked primary sources. Examples are illustrative, not product tests or earnings forecasts. This is general information. See our disclaimer.
Illustrative photograph by Kelly Sikkema on Unsplash. The image does not show an AI tool or a recommended service.
