https://blueprints.coevera.com/ Implementation blueprints for Coevera CRM (formerly Pipeliner). Each one starts from a business problem and documents the working configuration end to end — data model, fields, automation, limits and verification. en Wed, 09 Sep 2026 09:00:00 +0000 https://blueprints.coevera.com/blueprints/handover-from-sales-to-delivery/ https://blueprints.coevera.com/blueprints/handover-from-sales-to-delivery/ Wed, 09 Sep 2026 17:00:00 +0000 Handover Blueprint 010. Handing a won deal to the team that delivers it, in Coevera: give delivery its own pipeline and clone the won opportunity into it rather than extending the sales pipeline, because one record moving through two lifecycles corrupts conversion rate, sales cycle and weighted forecast alike. Covers the conditional clone, per-service quantity defaults, one process per source pipeline instead of one with a mega-condition, the four-way fan-out from the go-live date, why every automatic setter wants a re-runnable manual twin, and the backfill jobs a snapshot clone always ends up needing. https://blueprints.coevera.com/blueprints/automating-on-integration-owned-fields/ https://blueprints.coevera.com/blueprints/automating-on-integration-owned-fields/ Fri, 04 Sep 2026 09:00:00 +0000 Integration Blueprint 009. Most CRM automation branches on fields the CRM did not produce — subscription status, contract dates, seat counts, replicated from billing or an ERP. Treat them as evidence rather than state: mirror them read-only, derive a small CRM-owned layer that automation actually branches on, and add sync-health fields. Documents what a multi-day replication outage did in production — change-triggered automation silent rather than failed, scheduled automation running confidently on stale data, a catch-up burst stamping the wrong dates, exact-match conditions skipped permanently, and a freshness gate that disabled the check it was protecting. https://blueprints.coevera.com/blueprints/forecasting-renewals-before-they-exist/ https://blueprints.coevera.com/blueprints/forecasting-renewals-before-they-exist/ Thu, 03 Sep 2026 17:00:00 +0000 Automation Blueprint 008. Renewal forecasting separates two questions that get conflated: what a signed deal already commits, answered by a native revenue schedule that spreads value across dated month, quarter or year periods with a cancellation date for churn; and whether the customer will renew, answered by a native opportunity recurrence rule whose AfterNMonths and AfterNYears cadences match a contract term. Explains why creating renewal opportunities years in advance degrades conversion, cycle time and weighted forecast. https://blueprints.coevera.com/blueprints/pricing-one-product-many-prices/ https://blueprints.coevera.com/blueprints/pricing-one-product-many-prices/ Thu, 03 Sep 2026 16:00:00 +0000 Pricing Blueprint 007. A product in Coevera carries no price — the price lives on a join record between the product and a price list, along with its currency and a per-role access setting. Documents the asymmetry that creating a product generates price rows for existing lists but creating a list generates nothing for existing products, and the verified fact that the API never resolves a price from a list: line items created without an explicit price land at zero. https://blueprints.coevera.com/blueprints/document-numbering-that-survives-production/ https://blueprints.coevera.com/blueprints/document-numbering-that-survives-production/ Thu, 03 Sep 2026 15:00:00 +0000 Numbering Blueprint 006. Auto number fields in Coevera: a segment-based pattern builder whose Autocount carries a native "Reset count every year" option — so the common advice to compose year-prefixed numbers in an automation process is unnecessary. Documents the pattern grammar and its start index, the {year, month, count} counter state, and the rule for changing a pattern later — send it without the trailing start number, or the series restarts at that number and re-issues values already in use. Also covers the limits no configuration removes: gapless numbering, and a year that must come from a date other than the creation date; and the one case where a composition process is still the right answer. https://blueprints.coevera.com/blueprints/contact-migration-without-data-loss/ https://blueprints.coevera.com/blueprints/contact-migration-without-data-loss/ Thu, 03 Sep 2026 10:00:00 +0000 Data migration Blueprint 005. A 91-column, 3,432-record contact export. Migration failures are silent by default: a dropdown value with no matching option in the target lands empty with no error — 579 records, 17%, on one field alone. Covers why a sample export misleads in both directions, why the file is several cohorts rather than one list, which standard fields are CRM-managed and cannot be imported, and the post-import fill-rate comparison that is the only signal of loss you get. https://blueprints.coevera.com/blueprints/quote-approval-thresholds/ https://blueprints.coevera.com/blueprints/quote-approval-thresholds/ Wed, 02 Sep 2026 16:00:00 +0000 Process control Blueprint 004. A real approval gate on quotes above a value threshold: the threshold is an ordinary filter node, the enforcement is record locking rather than a notification, and approvers route to a role type that survives staff changes. Covers the three-call setup sequence, the decision nodes, and the expiration setting that silently auto-approves anything nobody answers. https://blueprints.coevera.com/blueprints/where-should-this-data-live/ https://blueprints.coevera.com/blueprints/where-should-this-data-live/ Wed, 02 Sep 2026 14:00:00 +0000 Data model Blueprint 003. A decision framework for placing a new requirement: six verdicts before any modelling — live, toggled off, config, build, hard limit, or not a product problem. In one six-department exercise 11 of ~44 requests were switches rather than builds. Then, when it is a build: field, sub-type, related child record, or custom entity, with the standing cost of each. https://blueprints.coevera.com/blueprints/ai-fields-read-documents/ https://blueprints.coevera.com/blueprints/ai-fields-read-documents/ Wed, 02 Sep 2026 09:00:00 +0000 AI fields Blueprint 002. Recognise once, read many — one AI field reads the attached documents and writes a JSON worksheet; every other field is a cheap text reader. Covers supported field types, why every AI-to-AI dependency must be its own process, asynchronous completion triggers, and the failure modes that report success while writing nothing. https://blueprints.coevera.com/blueprints/one-entity-five-request-types/ https://blueprints.coevera.com/blueprints/one-entity-five-request-types/ Wed, 02 Sep 2026 00:00:00 +0000 Data model Blueprint 001. One custom entity, five CustomEntityType sub-types, the native typeId as discriminator — one queue and one reference-number series carrying five different field sets. Covers why a custom type dropdown cannot work, why five separate entities also fail, the auto-default sub-type trap, and the proxy-Quote pattern required because approval processes cannot target a custom entity.