How does a project start?

It starts with a conversation about the current process, what should work better, and which outcome matters. From there we shape discovery and recommend a coherent scope, without forcing AI or a specific tool.

Which process is worth automating first?

A strong starting point is work that already happens every week and depends on copying data, chasing someone, or checking the same status in different places. When the operation repeats manual effort just to move forward, automation and integration often create quick value without a major routine change.

When is an internal system better than spreadsheets and loose tools?

When the operation depends on many manual updates, loses context across teams, or needs requests, owners, and status in one place. At that point an internal system stops being a luxury and becomes the simplest way to keep the process organized and usable day to day.

Do you work on one-off projects or monthly retainers?

Both are possible. Work can be a defined delivery, or continue for a few months to build, monitor, and improve an operation. The format is clear in the proposal and agreement.

Does every solution need AI?

No. AI only enters when it truly improves the outcome. In many cases a solid integration, automation, or internal interface solves the problem with less complexity and more predictability.

Is Mancilha an official Docusign partner?

No. We act as an independent consultancy for Docusign CLM and eSignature. Mancilha is not an official partner or affiliate of Docusign; the work is to organize the contract process and configure the solution around how the company actually operates.

How is the timeline defined?

After initial discovery, the scope is broken into stages with assumptions, dependencies, and acceptance criteria. The timeline comes from the work required, not from a generic promise before the process is understood.

What exactly is delivered?

It depends on the process: automation, integration, a portal, a dashboard, or a combination. The commitment is to deliver the operation running, with publishing, acceptance criteria, and documentation defined in scope, not just a tool left for the client to finish configuring.

What happens after delivery?

Delivery can include publishing, documentation, training, and support, depending on scope. We can also agree on a follow-up period to measure usage, fix friction, and evolve the solution.