Build with us

Build with Nori Works

If you like clear workflows, good interfaces and small robust systems, send a short introduction. Automation, internal tools, n8n, LangGraph, APIs and product-adjacent experiments are especially interesting.

Introduce yourself

What this is

Selected collaboration, not a job board.

Nori Works stays founder-led. This is not about staffing a large agency team. It is about finding sharp collaborators for selected systems, automations and product ideas.

How I think about work

With AI, roles get more fluid.

I believe technical work will be tied less tightly to classical job titles. AI makes individuals more capable, but it does not remove the question of what kind of work a product actually needs right now.

An early product needs different strengths than a growing or mature system. So I increasingly think in five roles that can change over the life of a project: Prototyper, Builder, Sweeper, Grower and Maintainer.

The interesting people are those who can inhabit one or more of these roles well and notice when a project needs something other than their preferred way of working.

  1. 01

    Prototyper

    turns new ideas into something concrete quickly, even if much of it does not survive.

  2. 02

    Builder

    turns a prototype into a usable system that can carry real work.

  3. 03

    Sweeper

    cleans up UI, code, workflows and complexity when friction becomes the bottleneck.

  4. 04

    Grower

    improves an existing product through real usage, feedback and clear priorities.

  5. 05

    Maintainer

    keeps a mature system reliable, secure, fast and maintainable.

Open directions

Two kinds of building together are interesting right now.

This is for people who think technically, build reliably and can get to working depth quickly when the topic fits, rather than a fixed role with a polished description.

Workflows, interfaces, systems

Automation Engineer / Workflow Builder

For someone who can turn recurring work into clear workflows and move pragmatically between code, tools and existing systems.

  • APIs, n8n or Make
  • LangGraph, small scripts and internal tools
  • Handoffs, approvals and monitoring
  • Operational reliability over demo effect

Prototypes, tools, product ideas

Product-minded technical collaborator

For someone who likes turning a real problem into a small useful product: clean enough to test, concrete enough to keep building.

  • SaaS prototypes and small web apps
  • Product-adjacent experiments
  • Technical sparring on architecture and implementation
  • Tools that could stand on their own

Open note

Not an exact match?

If you build in a similar direction, introduce yourself anyway. Concrete examples, small shipped systems, product ideas, or ways of working are more useful than a formal application.

Good fit

What makes collaboration easier.

  • You can build and ship small working systems.
  • You think in workflows, interfaces, edge cases and handover.
  • You write clearly and are comfortable working async.
  • You use AI tools, but not carelessly.
  • You care about reliability, data and human approval points.

Contact

A short, concrete introduction is enough.

Helpful are 2 to 3 sentences about you, a few examples or links, your favorite tools, and what you would like to build on. No formal cover letter needed.

Helpful would be:

  • Who you are and what you like working on
  • 1 to 3 examples, links, repos, demos or screenshots
  • Tools you are confident with: code, n8n, Make, LangGraph, APIs, internal tools
  • What kind of collaboration would be interesting for you
  • Roughly how much time you realistically have

Please do not send sensitive customer data or confidential project material.

Introduce yourself