Timerise Builders: Build Your Own Business on Our Skills

by Mateusz Sowa

Everything we know how to build is public: the skills, the process, the review, the prices. The skills catalog holds our Agent Skills, each one the way our engineers build a module they have shipped many times. Anyone can install them today.

What was missing is a way for people outside the studio to earn on them. That is Timerise Builders, our partner program. The first round is by invitation, and applications are open.

This post is about who we are looking for, and what we put under them.

Who we are looking for

Not employees, and not subcontractors billed by the hour. We are looking for people who want a business of their own: their own clients, their own pipeline, their own cash flow from project to project.

Most people who could do that never start, because a client project needs far more than the skill of building or selling. It needs a contract, a price list, infrastructure, a review process, a way to produce an offer quickly, and a name the client is willing to sign with. Building all of that takes years. We already have it, so we are putting it under the people who can use it.

Four kinds of people fit:

  • A developer who builds with coding agents and wants paid client work, without having to become a sales team and a legal department first.
  • A freelancer or a small agency whose clients already ask for booking, payments or screens in the venue, and who would rather deliver a proven module than invent one.
  • A salesperson who knows gyms, clinics, rentals or venues by first name and does not write code.
  • Someone a community trusts: an association, a franchise, a local network.

We are keeping the first round small on purpose. A few partners, certified one skill at a time. We would rather have a few people who deliver than a long list of sign-ups.

The umbrella: what Timerise carries

The idea is simple. You do the part you are good at. Timerise carries the rest.

What a project needsWho carries it
The contract and invoiceTimerise. The client signs one contract and gets one invoice, and Timerise is responsible for delivery
The brief and prototypeTimerise runs the brief and builds the clickable prototype in 48 hours
The priceTimerise, from the price list
The cost of a lost offerTimerise. The brief and the prototype are always paid by us, so a lost offer costs you nothing
Infrastructure and secretsTimerise. You build in our repository, and client secrets never leave Timerise
ReviewCI, an agent and a senior on every pull request
The offerOne document from Timerise, with your name on it

You also get the tools to sell and run projects: an offer generator that goes from brief to modules from the catalog to a price, materials per industry in English, Polish and Spanish, call scripts with the objections and the answers, and a public profile on timerise.ai with your badges and your own brief link. A brief that arrives through that link is attributed to you.

The client loses nothing in the arrangement. They get one contract, every line reviewed, and the code, documentation and IP handed over, as always.

The catalog is the product line

A business needs something to sell. Here it is the catalog. It keeps growing, so the table below is where it stands today and the catalog is the current list.

All but one build a module a client can buy. The exception, the skill eval loop, is a tool for the people who maintain skills.

An offer is a composition from that list. Take a gym that wants class booking and memberships. The offer names a booking kiosk at the entrance, Stripe Connect payments behind it and, in Poland, KSeF e-invoicing. Three modules from the catalog, a prototype attached, one price.

The catalog is also why this works for someone who is not a senior engineer yet. A skill is not a blank page. It carries the architecture, the hard rules and the tests of a module that has already been shipped, so a Builder starts from the reviewed version and the reviewer checks the work against a written list. We described what is in one in Our Agent Skills, and What Is Inside Them.

Certification follows the catalog too. It is per skill: you build one module from it on our infrastructure, it passes review, and you carry the badge for that skill, for example "Certified Builder · KSeF e-invoicing".

Four ways to earn

In any combination. Pick the ones that fit you.

  1. Bring clients. Introduce a gym, a clinic or a venue. Timerise runs the brief and builds the prototype.
  2. Connect communities. Open the door to a group you belong to and host a meetup with us. Timerise talks to the members.
  3. Run projects. Be the client's contact from brief to acceptance.
  4. Build modules. Build the module from a skill you are certified on, in our repository, under our review.

Partners are paid per project: a fixed share of the project value for each role, the same for everyone. Your share follows the roles you hold, so the person who brings the client, runs the project and builds a module earns on all three.

We have not published the shares yet. They go public when the first round opens, and we would rather say that here than have you guess.

From the first module to your own clients

The path has five steps.

  1. Apply. Tell us what you want to do and the skill you want to start on.
  2. Certify on one skill. Build one module from it on our infrastructure. Pass review, and you are certified.
  3. First project. A Timerise lead is at your side for the whole of it.
  4. Your own clients. Bring them with your own brief link.
  5. Senior builder. Certified on three skills and reviewing others, or maintaining one skill. From here you write custom logic beyond the skills and lead projects.

Referrers and Ambassadors do not have to walk it. They are roles, not levels, and neither ever has to become a Builder.

The reputation you build along the way is yours. Every badge carries a date and a link to its proof: the merged pull request, the module a client accepted, the first project from a community you connected.

Why every line is reviewed

A Builder pushes to the project branch. Three gates stand between that push and production: CI on every push, an agent that reads the pull request against the skill line by line, and a senior who looks at what the agent flagged and at the architecture. Merging and deploying is done by a senior or by Timerise, never by a Builder.

That can sound like a limit. It is the reason the rest is possible. The client can sign one contract with Timerise because Timerise has read every line, and you can sell a system without carrying the delivery risk alone.

What it is not

Better said now than after you apply.

It is not a job. There is no salary. You are paid per project.

It is not white label. The client always signs with Timerise. Your name is on the offer, not on the contract.

It is not a way around review. Custom logic outside the skills belongs to a Senior builder. Access to a project ends with the project.

It does not lock up the skills. They are MIT and stay that way. You can install any of them and build for your own clients on your own contract. The program covers projects contracted through Timerise: the infrastructure, the review, the price list, the prototype, the brand and your share.

How to apply

The application takes two minutes and needs no account: your name, country, the languages you work in and the roles you want. A GitHub or LinkedIn profile helps.

Contributors go first. A merged pull request to any skill in the skills index earns the Contributor badge and a place ahead of the queue. If you want to show us how you work before we talk, that is the shortest way.

The full program, with the roles, the badges and the permissions table, is at timerise.ai/builders.

Further reading