Where it started: accounts, AI scoping and talent matching

Most people with a product idea have the same problem. They know what they want, but not what it will cost, who can build it or how to start. Asking a developer for an estimate produces a number that depends on who you asked. Posting a job produces applicants before there is a clear brief to apply to. The blank page is the hardest part, and it is the part nobody is paid to help with.

Afren began as an answer to that: describe the idea in plain language, and get back a plan and the people to carry it out. The first release, shipped at the end of May, covered the whole path in outline, from sign-up to a payment. Everything since has been about making each step stronger. This article describes how that first path was put together, and why the steps come in the order they do.

From a sentence to a scope

You start by describing your idea in plain language. A sentence is enough to begin, and more detail gives a sharper result. Afren returns a structured scope: the product summary, the core features, the pages you need, the skills the work calls for, the project documentation, a budget and an estimate of the talent required. You leave with something concrete to react to, instead of a blank page.

If the scope missed what you meant, you can add clarifications and have it produced again. Nothing moves forward until you say the scope is right. Confirming is a separate step from reading, and it cannot be skipped: the platform refuses to confirm a budget until the scope has finished being written. That order is on purpose. A scope is the shared brief for everything that follows, including the designs, the build and any talent you hire, so it deserves a deliberate yes.

Each scope also comes with a review of the risks and of the market fit. The point of showing weak spots early is that they are cheap to change while the project is still a document.

A budget check that tells you before it matters

If your budget does not cover the scope, we tell you, show the analysis behind it, and ask whether you still want to proceed. You choose how to continue. The alternative is to say nothing and let you discover the gap when the first invoice arrives. A product that is honest about a shortfall at the planning stage costs you an adjustment. One that is silent costs you a project.

Finding the right people

From your confirmed scope, Afren suggests talent whose skills fit the work. You review their profiles and invite the people you want by email, or swap anyone out for another match. Browsing and searching the network yourself is possible too, so the suggestion is a starting point and not a decision made for you.

The path from invitation to work is modelled as a defined sequence of stages: scoping, matching, selection, invitation, and an active project. Each stage lists exactly which stages may follow it. A talent cannot accept an invitation to a project that has been archived, and a project cannot jump to active before the people on it have answered. Illegal moves are rejected rather than quietly allowed. Repeating a step that has already happened changes nothing, so a retry after a poor connection is safe.

Here is how the exchange works in practice.

• Invites. Talent receive an invitation and can accept or decline it from a dedicated page or from the link in the email.
• Proposals. A talent who has accepted an invite can submit a proposal with a price, a timeline, a cover note and milestones. Only invited talent can submit one, and only after accepting. The client is notified when it arrives.
• Awards. The client reviews the proposals and awards the work. Both sides can see where a decision stands, so nobody is left wondering whether a message was received.
• Starting. The project becomes active when every invited talent has accepted. If someone declines, the client can look for a replacement without starting again.

Showing what talent can do

A CV says what a person claims. Two features add evidence. The pre-interview is a short voice and video conversation with an AI interviewer, and its result is added to the talent's profile. Skill assessments let talent demonstrate what they can do on a specific subject. Together they give a client something more to go on than a list of past employers, which matters most when the client and the talent have never met and may live on different continents.

Wallet, chat and dashboards

Fund your wallet, receive payments and withdraw. The wallet works with US dollars, naira, cedis, Kenyan shillings and rand, with a currency converter for people who work in more than one currency. The ledger itself is kept in one currency, so balances stay consistent for both sides of a contract, and conversion happens where money enters or leaves. That design carried forward into escrow, which now sits on top of it.

Around the money sit the things that keep a team informed. Project chat lets the people on a project talk in one place. A notifications panel tells you when something needs you, such as an invite accepted or a proposal received. Dashboards for clients and talent show what is open, what is waiting and what has changed since you last looked.

Accounts and onboarding

Sign up with email or a social account, verify your email, and set up your profile as a client or as talent. Each role gets the setup that fits it: a client describes the company and what they want to build, and talent describe skills, experience and availability, which is what Afren matches against. You can read more about how each part works in the documentation.

What this means for you

You can move from an idea to a written, costed plan in one sitting, and see whether your budget fits before you commit to anything. You can find people whose skills match and invite them, and every decision on both sides is visible. Everything built since rests on this first path.