Vantnod

Vantnod CRM

Planned

Customer relationships that don't disappear into the inbox.

A sales relationship scatters across the everyday: contacts live in the inbox, the pipeline in a spreadsheet, and next steps in memory. When the deal moves on, the data does not move with it, and at invoicing the same details get typed again.

Vantnod CRM is in design: contact cards, pipelines, and activities will share the same data model as quotes, projects, and invoices. Nothing is re-typed, and the handoff from a won deal to an invoice is one click.

We are recruiting a design cohort now. The cohort sees the plans first, influences the feature order, and joins the founding pricing before the public opening.

Request accessSee Vantnod Studio
01Contact cards

Relationships and history · planned

02Pipelines

Stages and reasons · planned

03Activities

Calls and next steps · planned

04Invoicing

Handoff to Studio · planned

05Aino

Summaries fair use · planned

EU data · Aino fair use · Audit trail by default · A human approves every send · No re-typing · Direct human support

Planned

Contacts and companies

01 / 07

One card per relationship, the whole history attached.

The planned contact view gathers contact details, people, open deals, and past activities into one card per relationship. The card builds on the same customer registry Vantnod Studio already uses, so data never moves between systems.

  1. [01]

    Company card

    Contact details, billing details, and business id in one card, shared with Studio's customer registry. (planned)

  2. [02]

    People

    Several contacts per company, with roles and responsibilities spelled out. (planned)

  3. [03]

    Relationship history

    Quotes, deals, projects, and invoices as one history per customer. (planned)

  4. [04]

    One registry

    The same card feeds the quote, the project, and the invoice without copying. (planned)

Studio's customer registry is live today. The CRM contact view builds on top of it, not next to it.

Planned

Pipelines

02 / 07

Deals visible as a queue, not held in memory.

The planned pipeline view shows deals by stage: drag a deal forward, mark a win or a loss with its reason, and see what is waiting in each stage. This is the same Deals pipeline that is in preview inside Studio.

  1. [01]

    Stages by dragging

    A deal moves from stage to stage with one gesture, and the history stays. (planned)

  2. [02]

    Win and loss with reasons

    Every closed deal records the reason, so the next deal learns from it. (planned)

  3. [03]

    Shared Deals pipeline

    The same pipeline serves CRM and Studio, not two separate queues. (planned)

  4. [04]

    Pipeline health

    See where deals are stuck and what needs a decision. (planned)

Deals is already in preview inside Studio. CRM brings the same pipeline to the sales-work point of view.

Planned

Activities and timeline

03 / 07

Calls, meetings, and next steps on one timeline.

The planned timeline gathers the events of a relationship in one place: calls, meetings, notes, and agreed next steps. Nobody guesses what was promised, because the promise is visible on the timeline.

  1. [01]

    Calls and meetings

    Log the conversation straight onto the relationship timeline, with participants. (planned)

  2. [02]

    Notes

    Notes stay attached to the relationship, not as loose files. (planned)

  3. [03]

    Next step

    Every open deal carries a named next step and a date. (planned)

  4. [04]

    Reminders

    A promised call-back reminds you before the relationship cools. (planned)

The timeline is CRM's memory: it makes the relationship shared, not dependent on one person's memory.

Planned

From won deal to invoice

04 / 07

The accepted quote becomes a project and an invoice draft.

This handoff is the product's reason to exist: when a deal is won, the accepted quote becomes a project and the logged work becomes a reviewable invoice draft without re-typing. The Studio side is live today, the CRM side is planned.

  1. [01]

    Win with one selection

    Winning the deal starts project creation from the quote lines. (planned)

  2. [02]

    Project ready-made

    Phases and tasks are born from the accepted quote, not from a blank page. (planned)

  3. [03]

    Invoice draft

    Studio assembles an editable invoice draft from the logged work, as it does today.

  4. [04]

    A human approves

    The invoice leaves only when a human approves it, every time.

Example view of the product. Every figure is illustrative, not customer data.

CRM · Deal to invoiceExample
DealExample Company · won
QuoteAccepteddone
ProjectCreated from the quote
Invoice draftAwaiting review

Illustrative view · No customer data

Planned

Aino assistance

05 / 07

Summaries and next steps as suggestions, not decisions.

The planned Aino assistance condenses the relationship history and suggests the next step, with sources shown. Assistance sits inside the fair-use quota per company, and a human always decides.

  1. [01]

    Relationship summary

    Aino condenses a long history into a brief that prepares the conversation. (planned)

  2. [02]

    Suggested next step

    A suggestion with its reasoning and sources; approval always stays with a human. (planned)

  3. [03]

    Sources visible

    Every suggestion shows which data it was derived from. (planned)

  4. [04]

    Fair use

    Assistance is a fair-use quota, not tokens or sessions. (planned)

Planned

Pricing

06 / 07

Pricing is published before the opening.

Pricing is published before the cohort opens. The design cohort joins the founding pricing.

Join in

Design the CRM that closes the chain.

The design cohort sees the plans first and shapes how a customer relationship turns into an invoice without re-typing. Tell us what your sales chain looks like today.

Request accessSee Vantnod Studio

Planned · Founding pricing · EU data · jami@vantnod.com