Frequently asked questions

DejaDo builds practical automation systems for UK SMEs. You choose the repeated admin problem, and DejaDo scopes and builds the system around the tools your business already uses.

No. DejaDo is an automation consultancy, and we keep the whole thing in plain English. The work starts with your process, your data, and the outcome you want, not the tools underneath it. You will always know what we are building and why.

Process Snapshot is a short pre-sale review route for owners who can describe the manual process they want fixed. It helps DejaDo understand the bottleneck before suggesting Lite, Pro, or no-fit.

No. It is reviewed before DejaDo responds. It is not an instant quote, product selector, proposal, or implementation specification.

DejaDo reviews the answers and replies with the sensible next step. That may be a Lite fit, a Pro discussion, a request for missing information, or a polite no-fit.

Lite is fixed-scope automation for common SME admin bottlenecks. It is tailored to your existing tools inside clear rails, with final scope and pricing confirmed in the SOW.

The current Lite systems are Invoice Chaser, Quote Follow-Up, Lead Responder, Missed Enquiry Responder, Review Collector, Appointment Reminder, and Client Welcome Sequence.

The Lite care plan covers monitoring, basic issue checks, and small agreed fixes. Final care allowance, term, volume caps, third-party tool costs, and pricing are confirmed in the SOW.

Lite has public from prices, but the final price is confirmed in the SOW after scope, tools, prerequisites, volume, third-party costs, and exclusions are checked.

DejaDo will say so. Bigger work is usually scoped as Pro when it involves deeper process design, multiple systems, scoring, complex routing, or compliance-heavy workflows.

Pro is diagnostic-led custom automation for bigger or messier operational problems. It is used when the work needs discovery, judgement, process design, multiple systems, or a business-case check before a quote.

Yes, where it is scoped. Ongoing support is agreed separately in the SOW, including what is covered, what is excluded, and how change requests are handled.

Because the final Lite cost depends on the tool setup, access, data quality, volume, third-party costs, and exclusions. Public Lite prices are starting points, not binding quotes.

Usually no. Tool subscriptions, SMS, WhatsApp, call tracking, review platforms, booking tools, CRM fees, and similar costs are separate unless the SOW says otherwise.

Small care-plan work may fit inside the agreed Lite care allowance. Work outside agreed scope is quoted separately before it starts.

Yes. Standard usage limits apply. Final volume cap and care terms are confirmed in the SOW.

DejaDo commonly works around accounting tools, CRMs, calendars, booking tools, forms, email, spreadsheets, review platforms, and similar SME systems. Tool fit is checked before quoting.

Usually no. Lite is designed around your current tools where they can support the agreed process. If a tool cannot support the work safely, DejaDo will flag that before the SOW.

Do not send passwords through the website. Where access is needed, DejaDo prefers OAuth, secure vault access, or another approved secure method after scope is agreed.

Do not send passwords, secrets, sensitive personal data, medical or care data, payroll or HR records, legal dispute details, regulated financial data, or large customer exports through the website.

Sometimes, but those channels need separate review because they can add vendor, consent, data, and usage-cost questions. If included, the SOW will state the scope and costs.

DejaDo keeps first projects low-risk and tightly scoped. Health, care, children or vulnerable-person data, payroll or HR records, legal disputes, regulated financial work, emergency systems, and automated decision-making over personal data need separate review and may be declined.

No. DejaDo builds the system and agrees functional acceptance checks. It does not guarantee revenue, customer behaviour, lead volume, payment speed, review volume, or review scores.

The SOW should define functional checks such as whether reminders send correctly, stop conditions work, records are updated, and notifications reach the right person.