Cadrientby Arthoken
How Cadrient works

How we build your team’s app.

Start with one process. Arthoken builds a free, private prototype around your forms, roles and decisions. Your team tries it before deciding whether to invest in a production app.

Inside the application

Keep every request moving.

A case brings the request, people, documents and decisions together. The workflow determines what happens next.

  1. Capture the request

    Collect the relevant answers and documents in a form shaped around the process.

  2. Give someone a clear next step

    Route work to the right person, show what is missing and keep deadlines visible.

  3. Review and decide

    Check evidence, ask for corrections and record the required approvals. Keep discussion with the case.

  4. Resolve it with a record

    See what happened, who decided and what remains outstanding. Review progress across the team.

Working with Arthoken

From exploration to your application.

We begin with one agreed process. The prototype helps your team judge the fit before its production release.

  1. Explore and tell us what you need

    Watch a walkthrough or try the fictional demo. Send a short enquiry about your team’s process.

  2. Agree the scope

    We choose one workflow, the people involved and an example your team wants to test. We put the prototype scope and review date in writing.

  3. Review your private prototype

    Your project gets a separate codebase, adapted from the Cadrient foundation. Review your forms, terminology and workflow using fictional examples, and agree any changes.

  4. Prepare, launch and maintain

    If you’re happy with the prototype and accept the production scope and price, we prepare your own deployment. Before live use, we validate its access controls, data storage, files and recovery. Hosting, updates, support and ongoing costs are agreed for your project.

Sample prototype scope

Laptop requests for new starters

Priya starts on Monday. The $800 laptop her manager approved is out of stock. A supplier offers a $2,500 replacement. Purchases of $2,000 or more go to Finance.

We agree which steps to include and when you’ll try them. The initial prototype is free.

What you supply
Two fictional purchase requests, your intake fields, approval threshold and the people responsible for each decision.
What you receive
A private, working prototype with a request form, an approval queue, both approval routes, a delivery step and a history of the IT receipt. Your application has its own codebase.
What you try at the review
Try $800 and $2,500. Check which request needs Finance. Record a dispatch reference, confirm receipt as IT, then check who approved and who received the laptop.
What comes after
If you’re happy with the result, you can agree a separate production scope and price covering live sign-in, purchasing-system connections, deployment and support. If you stop after the review, you owe nothing.

A second complete example: client onboarding

Follow Northstar Labs through intake, missing documents, reviewer approval and kickoff handoff. Its approval depends on checked documents and reviewer permissions, while the equipment workflow uses a purchase threshold.

Read the onboarding walkthrough · Try client onboarding

See the free prototype scope, pricing structure and enquiry next steps

Which process would you like to improve?

Start with a short description. We’ll discuss the details with you.

Request a prototype