Cristian Nichifor
Menu

PROCESS AUTOMATION & INTEGRATIONBuilding in Coda since 2022

Operations that run themselves.

I replace inbox approvals, spreadsheet chains and copy-paste between tools with connected workflows in Superhuman Docs (formerly Coda), Fibery and n8n. Then I stay on to keep them running.

Talk to Cristian · 30 minHow it works and prices
  • Purchase requests approved with one button
  • A closed deal becomes a project with tasks
  • Invoices created when the work is approved
  • Client onboarding that runs the same way every time
  • A weekly report built from live data
  • Website leads land in the CRM with an owner
  • Timesheet reminders before anyone is late
  • A failed step that pings a person, not a log

Workflows I build · examples

…and the one your team keeps doing by hand.

Sounds familiar?

The tools multiplied. The process didn’t get clearer.

It started as one doc and a spreadsheet. Now there are forty docs, three ways to log a request, and one person who understands the formulas. When they’re away, nothing gets fixed.

  1. The doc takes ages to load.

    Heavy formulas, cross-doc syncs and tables nobody archived.

  2. Automations fail quietly.

    You find out when a client asks why nothing happened.

  3. People went back to spreadsheets.

    Because the system was built for the builder, not for them.

Is this you? Tick what’s true

Book the 30-minute callNot yet? Read my notes

Which tool

The right tool for how you work.

I start from the process, then pick the tool. Often it’s a combination: a workspace where people do the work, and an integration layer that moves data between systems. Licences are paid by you directly to the vendor.

  • Superhuman Docs

    Best when the process lives in docs and tables people already edit

    First build: a request flow with an owner, a status and one button for the next step.

  • Fibery

    Best when everything needs to link up: clients, projects, tasks, feedback

    First build: a connected model where a closed deal becomes a project by itself.

  • n8n

    Best when the work crosses tools: forms, CRM, email, invoicing

    First build: an integration with a failure path that reaches a person.

Superhuman Docs (formerly Coda), Fibery and n8n are trademarks of their respective owners and are named here to describe the tools I work with.

What I build

The building blocks.

You don’t buy these one by one. The audit decides which ones matter, and the monthly engagement builds them in that order.

  • Start

    Process walkthrough

    One real request, followed through every tool and person it touches.

    → Recorded walkthrough + priorities

  • Fix

    Workspace health

    Speed, formulas, permissions and automations in an existing Superhuman Docs or Fibery workspace.

    → Report, quick wins done

  • Plan

    Process mapping

    Every step and handoff, mapped with the people doing the work.

    → A process map you keep

  • Build

    Custom workspace

    Request flows, CRMs, project hubs and dashboards, built around your team.

    → Working system, demoed weekly

  • Connect

    Integrations

    n8n workflows or custom Coda Packs to your CRM, finance and chat tools.

    → Tested integration + docs

  • Move

    Migrations

    Out of spreadsheets, Notion, Airtable or an old doc, without moving the mess.

    → Clean data in the new system

  • AI

    AI-ready workspace

    Data structured so the AI features in your tools answer from the right source.

    → Clean structure + prompts

  • Run

    Training & care

    Hands-on sessions before go-live; fixes and small changes after.

    → Part of every monthly pace

TRY A SAMPLE WORKSPACE

The work changes. The shared view follows.

This fictional example shows how I’d connect a business problem, a working solution, and the questions we need to ask about adoption.

Here’s what I’d look at first.

An illustrative scenario, with goals we would agree and test together.

  1. The problem

    Requests arrive through different channels. The team cannot easily see who should act next.

  2. The working solution

    I’d start with one shared request record, an owner, and a next action. The example below lets you try the idea by completing a fictional request.

  3. Team adoption

    We’d walk through a real handoff with your team, including what happens when someone is unavailable. Then we’d check whether people can find their next action without asking around.

SAMPLE DATA

An example success plan

Goal
Make responsibility visible at each handoff.
Success criteria
Every pilot request has an owner; users can identify the next action. To be validated.
Client owner
Operations lead — illustrative role.
Next milestone
Walk through a representative request with the team.
Open decision
Who handles a request when its owner is unavailable?

My starting point: clarify who owns the next action before automating the handoff. — Cristian

Team operationsSAMPLE DATA

What needs attention?

Requests
4
Open
4
Completed
0
Fictional team requests
RequestOwnerDueStatusAction
Review website contentMaraTodayIn review
Prepare proposal outlineAlexTomorrowIn progress
Follow up on support requestAndreiTodayReady
Update operations summaryMaraFridayReady

Try completing a request. The counts and filtered views use the same sample records.

Interactive example with fictional records. No account is connected; your changes reset when you reload.

Try it yourself

From request to confident handover.

A live Superhuman Docs workspace with fictional records. Pick a request, give it an owner, and see what the team needs before it is handed over. Nothing you change is saved.

Fictional example · changes are not saved

Open the full demo

The demo loads from docs.superhuman.com only after you press the button.

On a narrow screen the full demo is easier to use.

PACKS & CUSTOM INTEGRATIONS

Bring the data into the workflow.

Explore the Google Contacts beta and two packs that are coming soon. Each example shows its current status; public installation availability is not confirmed here.

CONTACTS & CONNECTED WORKFLOWS

Google Contacts for Coda

Beta

A Pack for contact tables and groups in Coda. The source is available to explore; public installation and sync operations still need validation.

  • Coda Pack
  • Google Contacts
  • Beta
Explore the source

ACCOUNTING INTEGRATION

Billy Pack for Coda

Coming soon

Billy accounting records in Coda, beside the work they inform. The Pack is being prepared for release; the example here uses fictional records.

  • Coda Pack
  • Billy API
  • Accounting workflows
Explore the project

CLOUD INVENTORY INTEGRATION

Hetzner Pack for Coda

Coming soon

Hetzner Cloud inventory in Coda, where resources can be reviewed alongside ownership and operational context. This Pack is being prepared for release.

  • Coda Pack
  • Read-only inventory
  • Cloud operations
Explore the project

How it works · prices included

Call, audit, then a pace that suits you.

Prices are here because you were going to ask. All prices exclude VAT.

Prices in

  1. 01 · Free · 30 min

    Intro call

    What’s broken, what you’ve tried, and whether these tools are even right for you. If they aren’t, I’ll say so on the call.

  2. 02 · €1,500 · 3–6 weeks

    Process audit

    I talk to the people doing the work, map every step and price what it costs today. Half up front, half when you’re satisfied. The plan is yours either way.

  3. 03 · Monthly

    Pick a pace and build

    Highest-priority work first, reviewed together as it lands.

  4. 04 · Included

    Launch and keep improving

    Your team is trained before go-live, with written guides and recordings. Afterwards I adjust the system as your work changes.

Steady

€2,300 / month

We talk once a month

One process at a time, at a steady rhythm.

FocusedRecommended

€3,450 / month

We talk every two weeks

A good default for most teams.

Sprint

€4,600 / month

We talk every week

When the plan has a deadline.

Same quality and scope at every pace: you choose how fast the plan moves and how often we talk. Month to month; give 30 days’ notice and that’s the last invoice. When there isn’t enough valuable work left to justify the fee, I’ll be the one to say so.

Tool licences (Superhuman Docs, Fibery, n8n) are paid by you directly to the vendor.

Illustrative scenario · not a client

A 25-person agency with requests in three inboxes.

What a typical engagement looks like. A sample situation, not a real client.

  1. 01Before

    Client requests arrive by email, Slack and a form. Account managers copy them into a spreadsheet. Approvals happen in direct messages. The Friday report takes half a day.

  2. 02What I’d build

    One intake form into a Superhuman Docs table. Every request gets an owner and a status. Approve with a button; n8n notifies the owner and creates the invoice line. A live dashboard replaces the report.

  3. 03After handover

    The team runs it. A one-page guide, recorded walkthroughs and a named owner for each step. I check in after 30 days.

The person you’ll work with

Portrait of Cristian Nichifor

Consultant & builder Copenhagen, Denmark

English · Romanian

There’s no junior. You work with me from the first call to the handover.

I’ve been building in Coda since 2022. For four years I did it quietly, as a freelancer: teams found me by word of mouth and through my posts in the Coda community, and I untangled their docs and built what they needed. When Coda couldn’t reach the tools those teams used, I started writing Packs: Google Contacts, Billy, Hetzner. In 2026 I became a SlideHub partner and put the work under my own name.

I still do every audit and every build myself, on site in Copenhagen or remotely anywhere. In my own time I write about how work, technology and public rules shape each other, and build open-source tools for public data.

More about me

Questions

Before you book.

01Is this Coda or Superhuman Docs?

The same product. Coda became Superhuman Docs; existing docs and Packs keep working.

02Do you work remotely?

Yes. I work remotely with teams anywhere in the world, in English or Romanian. On site is an option in Copenhagen.

03We already have a workspace. Can you work with it?

Usually that’s where I start: the audit looks at what you have before anything new is built.

04What if we want changes along the way?

That’s what the monthly engagement is for. New requests go on the plan and are prioritised against everything else. Nothing is billed outside the monthly fee.

05I only need help with one formula or automation.

Then I’m probably not the right fit, and the Superhuman, Fibery or n8n communities will help faster. I design and run whole processes.

06Who owns the work afterwards?

You do. Everything lives in your accounts, documented, with recordings. Nothing depends on me.

07Are you an official partner of these tools?

Not of Superhuman, Fibery or n8n: I work with them independently. I’m an official SlideHub partner.

08Do you work on site?

Yes, in Copenhagen: kick-offs and workshops in person. Everyone else, anywhere in the world, remotely.

Let’s talk

Show me the workflow your team keeps doing by hand.

30 minutes, free. You leave with a clear next step, even if it isn’t with me.

  • 01 · Fastest

    Book a call

    Pick a 30-minute slot in my calendar. Free, and no preparation needed.

    Choose a time

  • 02 · Simplest

    Write me

    A short form: what you want to improve and one example. I reply by email.

    Open the form

  • 03 · EasiestComing soon

    Send a voice note

    Talk for up to five minutes. It’s transcribed and summarised, so I come to the call prepared.

    Coming soon