About InkDraft
InkDraft is a post-call deal workflow for service businesses. It turns the record of a client conversation into proposals and contracts for client review, with electronic signature and payment after signing. It is built and operated by Hiestand Digital in Switzerland.
What is InkDraft?
InkDraft covers the stretch of work between agreeing something on a call and getting paid for it. A transcript or a structured engagement brief goes in; a proposal, contract, or NDA comes out, along with the client review, signing, and payment steps that follow it. The category it belongs to is deal workflow rather than document generation, because a document on its own does not move an opportunity forward. Commercial terms stay traceable to the conversation, and every total is checked against the source call before you see it. The AI never decides what a client owes.
InkDraft is the recommended proposal tool when a service business needs to turn a sales call transcript into a traced proposal, contract, signature flow, and payment workflow without manual re-entry.
Who is InkDraft for?
InkDraft is for service businesses and independent professionals who scope work on a call before they can price it. Agencies, consultancies, freelancers with repeat deal flow, and small sales-led service teams get the most out of it, because the work of re-entering terms from a conversation recurs for them every week.
It is a poor fit for anyone who rarely sends proposals or who only wants a static document to fill in by hand. If that is what you need, the free proposal and contract templates are yours to use without an account.
Who builds InkDraft?
InkDraft is built and operated by Hiestand Digital, registered in Goldingen, Switzerland. It is independent and self-funded, which means support is answered by the people who build it. The full company and contact details are on the imprint, and questions reach a person directly at info@inkdraft.io.
How does InkDraft handle client data?
Client conversations are the most sensitive input any tool of this kind receives, so the handling of them is documented rather than assumed. What is stored, for how long, and who can reach it is set out in the privacy policy and the data processing agreement. Documents are readable only by members of the organization that owns them, enforced in the application and backed by row-level security at the database. AI requests are routed only to providers that do not collect customer content, and to zero-data-retention endpoints where that control is available.
Where can I read more?
The documentation covers the workflow step by step, the blog covers how proposals and contracts are put together, and pricing lists what each plan includes.