The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Most integration documentation is written from interviews. Someone explains how the system is supposed to work, a writer transcribes it, and the doc captures the memory, not the system.
I do it the other way. I read the actual workflow exports, configs, and source, then document how the integration behaves in reality. When the doc and the system disagree, the system wins, because that's what I read.
The difference shows up later. Interview-based docs drift the moment a memory is wrong or a config changed after the conversation. Code-first docs match what's running, and every claim traces back to a specific artifact you can open and check 😍
Four full samples here, built on fictional but realistic scenarios: runbooks, a spec, a two-document package, and an architecture decision record, across n8n, Celigo, Salesforce, Zendesk, HubSpot, and NetSuite.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Challenges
View all
Related posts
A SaaS website can explain every feature perfectly and still leave one question unanswered:
Why should I care?
That's why CORESPACE includes Stories.
Instead of only describing what the product does, Stories give those features context — showing how they're used and what they make possible.
Features explain the product.
Stories make it relatable.
The “why should I care?” framing is exactly the right antidote to feature tours. Turning real team stories into the connective tissue between the product and its impact makes the homepage feel human, not just informative.
I was handed a logo and a color palette. The client needed everything else — the system that turns a few brand decisions into a working enterprise product.
The project: a from-scratch redesign of an eIDAS-compliant B2B signature platform. Legally binding document workflows, enterprise customers, zero room for ambiguity.
I built the system in a deliberate order: icons → tokens → components → screens. Each layer constrained the one above it. That order is the whole method — by the time the first screen was designed, the system underneath was already stable. Screens demonstrated the system instead of driving it.
The token architecture had three layers: global primitives, alias tokens that describe intent (surface.primary, border.subtle), and component tokens that bind intent to elements. Sounds academic — until the team grew and other designers started building on top of my foundation. Some of my decisions held. Others got changed.
The token architecture absorbed both without breaking. That's the only test that matters.
A system that can't be changed isn't a system — it's a style guide.
Full case study — the setup, the build order, and three surfaces where the system did real work: bozenabulat.com/projects/b2b-signature-platform-redesign
bozenabulat.com
B2B Signature Platform Redesign
A token-based design system for a B2B signature platform built on an enterprise CRM. Turned inherited brand foundations into a scalable architecture.
Good feedback needs a location. A decision needs a version.
I built FrameProof to bring both into one image-review workspace for designers and small creative teams.
Pin feedback directly on the artwork, keep replies beside the detail, compare revisions and record a decision on the exact version being reviewed. Private projects and expiring guest links keep the sharing workflow focused.
The design stays deliberately quiet: warm neutrals, a restrained terracotta accent and an uncropped canvas that gives the work room to breathe. Underneath it, React, TypeScript and Supabase handle the application, roles and private storage. Built with Bolt, then refined through focused engineering and testing.
The narrated walkthrough shows the complete workflow. The demo uses fictional artwork, so you can explore without uploading client files.
Case study: https://contra.com/p/UY3B7obe-frame-proof-visual-feedback-and-version-approval
Source kit ($99): https://contra.com/products/mHxtVfQw-frame-proof-or-visual-review-source-kit
What causes more friction in your review process: scattered comments or uncertainty about the final version?
