Services

Choose a service by the problem you need to solve.

Auranium helps with three things: clarifying the product before investing, building a product people can use, and coaching businesses to deploy AI Agent systems themselves.

Start from your team's current situation. You don't need to pick the right service name first.

Start from where you are

Where are you stuck?

You don't need to pick the right service name first. Choose the situation closest to your team and Auranium suggests where to start.

Product consulting

Suggested starting point

Product Consultant

Before hiring a build team, clarify the users, evidence and assumptions. The conclusion may be to build, adjust or stop.

  • Problem, users and current evidence
  • Main flow with in-scope and out-of-scope
  • Priorities and next decision
See service details ↓
Product consulting

Suggested starting point

Product Consultant

Consulting aligns goals, priority reasons and scope boundaries before every request gets pushed into one version.

  • Problem, users and current evidence
  • Main flow with in-scope and out-of-scope
  • Priorities and next decision
See service details ↓
Product development

Suggested starting point

Product Development

Design, build and test in rounds with a viewable version, so the team can give feedback before scaling.

  • A working product
  • Code and tests
  • User documentation and handover
See service details ↓
Product development

Suggested starting point

Product Development

Review code, architecture, data, permissions and tests to decide what to keep and what to reinforce before going to production.

  • A working product
  • Code and tests
  • User documentation and handover
See service details ↓
Coaching AI Agent

Suggested starting point

AI Agent Coaching

Four 1:1 coaching sessions: you install it yourself, connect tools, move the system to a server and set up cost control.

  • A working AI Agent system
  • Installation, configuration and troubleshooting guides
  • At least three real processes and the ability to maintain them
See service details ↓
Coaching AI Agent

Suggested starting point

AI Agent Coaching

High-frequency, standardised work is where AI Agents cut cost and time the most. The first three processes are chosen in session 1.

  • A working AI Agent system
  • Installation, configuration and troubleshooting guides
  • At least three real processes and the ability to maintain them
See service details ↓

Three service scopes

Choose by what the team needs to solve right now.

01Product Consultant

Product consulting: clarify before you invest in development.

For business owners, founders and teams who need to decide what to do first. Auranium works with you to clarify users, the problem to solve, the priority scope and the assumptions to validate.

You receive a set of documents the team can use to align on decisions, whether you build it yourself, with Auranium or with another development partner.

Build Adjust Stop

When to use it

Which decision is the team stuck on?

This service fits when the investment question is still open, requirements aren't aligned or the scope has no clear boundaries.

01

The idea isn't tied to users yet

There is an initial direction, but it's unclear who will use it and which problem is worth solving first.

02

Requirements conflict

Several parties make different proposals, without agreeing on goals or priorities.

03

The scope is too broad

The wish list is long, but what to do first and what to postpone isn't decided.

04

Not sure whether to buy or build

The team needs to separate process problems from tool problems before choosing software or AI.

If the product direction, main flow and scope are already clear, you can go straight to Product development

Core outputs

Documents organised around the decision to be made.

Each deliverable helps the team see what's known, what's uncertain and the boundaries of the next step.

  1. 01

    Problem and users

    Record the problem, users, evidence and assumptions to validate.

    Used forAlign the team on what is being solved and on what basis.
  2. 02

    Main flow and boundaries

    Describe the main usage flow, what's in and out of scope, and the reason for each limit.

    Used forAvoid putting every request into one version.
  3. 03

    Evidence-based priorities

    Weigh impact, strength of evidence, risks and dependencies instead of relying on a wish list.

    Used forKnow what needs doing or validating first.
  4. 04

    Next decision

    Record the actions, decision conditions, open questions and who needs to confirm.

    Used forChoose to build, buy a tool, validate further, adjust or stop.

How we collaborate

Every working round ends with something you can review.

You don't need a long specification. The starting point is your current situation and the decision you need to make.

  1. Intake

    You share your goals, current situation, existing documents and the questions to decide.

  2. Agree the scope

    Both sides agree the questions, outputs, responsibilities, review method and fee before starting.

  3. Analysis and validation

    Auranium cross-checks data, processes and user feedback within the approved scope.

  4. Review and handover

    Both sides review the proposal and record decisions, open items and next steps.

Handover structure template

One product decision, clarified.

Example: managing customer support requests — current state, evidence and scope side by side to weigh the next step.

Case · Managing customer support requests
Current state

Support requests arrive through many channels; the team needs to know who is handling what.

Evidence

Cross-check conversation history, how work is assigned and the cases that were missed.

Assumptions

One place to track status could reduce manual handoffs.

Options

Fix how work is assigned, use an existing tool or build a dedicated management flow.

Scope

Prioritise intake, owner and status; AI isn't in the flow yet.

To validate

Is the bottleneck a missing tool or unclear responsibility?

Additional scope

Expand only when the decision requires it.

The items below aren't included in every project by default. Auranium proposes them when needed and agrees them separately before doing them.

Demand validation

An interview or test plan, the questions to answer and the conditions to continue.

Interactive prototype

Used when a flow or way of working needs to be seen and given feedback before development.

Technical assessment

Review integrations, data, dependencies and risks when the decision needs more technical evidence.

AI opportunity assessment

Review data, execution rights, exceptions and approval points. The conclusion may be that AI isn't needed yet.

After consulting

You choose how to continue based on what was clarified.

Consulting creates no obligation to hire Auranium for development. The documents can be used by your in-house team or another development partner.

02Product & AI Development

Turn a business problem into a product that works in the real world.

You can start from a problem, a process, an idea or a prototype. Auranium helps clarify what to build, design the experience, develop the system, apply AI where it fits and take the product to production.

Starting points

You don't need a complete specification to start.

Many products start from a manual process, a prototype or changing requirements. The first job is to reduce the uncertainty about what to build.

01

The current process is too manual

Data entry, file transfers, checks and approvals make work slow or hard to track.

02

Have an idea but the MVP isn't clear

The feature list is long, but it's unclear which parts are needed to validate the direction.

03

Want to apply AI but don't know where to start

The use case, data, business rules and human approval points aren't clear yet.

04

Have a prototype that can't be put into use yet

The demo needs architecture, permissions, integrations, testing and operational monitoring.

What can Auranium build?

Digital products built around a specific business job.

Pick a product type to see where it's used. Technology changes by project; the starting point is always the users, the process and the smallest useful scope.

Multi-user product

01/10

SaaS

A platform serving many accounts or organisations, with clear sign-up, permissions, operations and administration.

Common use cases

Turn a repeatable process or service into a subscription product.

Self-service experience

02/10

Customer portal

A secure space for clients to view data, submit requests, track progress and receive deliverables.

Common use cases

Reduce scattered email back-and-forth and give clients a single point of access.

Internal operations

03/10

Internal operations system

A system that connects data, tasks, approvals and reports around how the business actually works.

Common use cases

Replace spreadsheets, file transfers and manual handoffs with a trackable workflow.

Multi-sided platform

04/10

Marketplace

A product connecting supply and demand, with profiles, search, transactions, controls and administration.

Common use cases

Create a trusted exchange mechanism between multiple user groups.

Bookings and service capacity

05/10

Booking platform

Manage availability, service types, bookings, confirmations, rescheduling and back-office operations.

Common use cases

For services with limited resources such as experts, rooms, equipment or time slots.

Browser application

06/10

Web app

A product with its own workflow, data and permissions, used directly in the browser.

Common use cases

Build business tools, dashboards, self-service platforms or B2B products.

On-device experience

07/10

Mobile app

Mobile experiences tied to on-site needs, notifications, camera, location or quick actions.

Common use cases

When the main work happens away from the desk or needs frequent interaction.

AI inside the product

08/10

AI-powered products

AI is placed in a flow with data, criteria, access control and a way to evaluate output.

Common use cases

Document understanding, search, recommendation, copilot, classification or extraction.

AI inside the workflow

09/10

Workflow automation

A chain of repetitive steps connected with integrations, business rules, approvals and exception handling.

Common use cases

Routing, drafting, reconciliation, knowledge retrieval, approval or system updates.

Industry-specific software

10/10

Industry software

A product designed around the operations, roles, data and control requirements of a specific industry.

Common use cases

When off-the-shelf tools don't reflect the real workflow and domain constraints.

Starting points

Start where your project still has the most uncertainty.

Each starting point addresses a different kind of risk. Pick one to see its scope and outputs.

When the scope is unclear

01 / 06

Product & AI Discovery

Define the problem, users, process, product scope, AI opportunities, risks and technical direction before committing to Build.

Outputs

Problem definitionMVP scopeBacklogTechnical directionRoadmapEstimate

When you need to test first

02 / 06

Prototype / Proof of Concept

Test user flows, experience or technical and AI feasibility before investing in the full system.

Outputs

PrototypeProof of ConceptFindingsFeasibilityRisksRecommendation

When the direction is clear

03 / 06

MVP & Product Development

UX/UI design, architecture, frontend, backend or mobile, integrations, QA, infrastructure, analytics and production launch.

Outputs

UX/UIArchitectureEngineeringIntegrationQAProduction

When work is too manual

04 / 06

AI & Workflow Automation

Map the workflow, design AI logic, business rules, approval points, integrations, exception handling and monitoring.

Outputs

Workflow mapAI logicBusiness rulesApprovalExceptionsMonitoring

When a demo needs real users

05 / 06

Prototype to Production

Review code and architecture, strengthen the data model, authentication, permissions, security, integrations, testing, monitoring and deployment.

Outputs

Code reviewData modelAuthenticationSecurityTestingDeployment

When the product is live

06 / 06

Improve & Operate

Monitor stability and usage data, fix bugs, improve flows, tune AI and build new integrations.

Outputs

MaintenanceAnalyticsIterationAI tuningPerformanceReliability

AI, but it must solve a real job

Apply AI where it improves a specific product or process.

AI sits inside a workflow with data, business rules, access control, exception handling and traceability.

  1. 01Input

    Documents, requests or operational signals are standardised before processing.

  2. 02Data & context

    Data sources, usage rights and background information are clearly controlled.

  3. 03AI processing

    Classify, search, extract, draft or recommend based on the goal.

  4. 04Business rule

    Business conditions decide which work continues, stops or is handed off.

  5. 05Reviewer

    Risky decisions stop at a checkpoint for a human to approve.

  6. 06System executes

    Actions are logged, fed back and brought into an audit loop for improvement.

From demo to real product

A prototype proves the idea. Production needs more than that.

AI and no-code make demos fast. Once real users arrive, the product needs data, access control, fault tolerance and a clear operating process.

Talk to us to discuss it together
  • Data model
  • Authentication
  • Permission
  • Security
  • Integration
  • Testing
  • Logging
  • Performance
  • Deployment
  • Maintainability

Development process

One end-to-end product process with clear decision points.

Every phase ends with a reviewable output. The client takes part in decisions about priorities, data and business rules.

  1. 01Understand

    The business problem, users, processes and constraints.

  2. 02Define

    Scope, requirements, success criteria and risks.

  3. 03Design

    User flows, prototypes, UI and validation.

  4. 04Build

    Architecture, development, integration and QA.

  5. 05Launch

    Production, analytics, monitoring and handover.

  6. 06Improve

    Feedback, metrics, improvements and post-launch support.

Auranium

Analysis, recommendations, Product, Design, Engineering and delivery management.

Client

Domain knowledge, access to users and data, priorities and commercial decisions.

01

Clear decision gates

No big build commitment while scope or risk is still vague.

02

Transparent scope

Assumptions, exclusions, dependencies, acceptance criteria and changes are all made explicit.

03

Deliverable outputs

Code, design and documentation are handed over according to the agreed scope and terms.

04

Human control when AI carries risk

Approval, logging and exception steps are designed right into the workflow.

031:1 Coaching Programme

Run your business with AI Agents.

A hands-on 1:1 programme for business owners and managers. After four sessions, you can deploy, configure and run an AI Agent system for your own business. No programming knowledge required.

04

sessions, 90 minutes each

1:1

One-to-one, one person

15

days of support after the programme

Context Tools Execution

Context

From using AI in chat sessions to running operations with AI Agents.

Most businesses use AI as Q&A and then copy the result into other tools. AI shortens each step but doesn't change the cost structure of operations.

Today

Using AI in chat sessions

  • Doesn't keep context

    Every session starts from scratch; products, clients and templates must be entered again.

  • Can't execute

    Results stop at text. Sending emails, updating spreadsheets and exporting files are still manual.

  • Not repeatable

    A process that runs 20 times a month needs 20 separate sets of instructions.

After the programme

Running on AI Agents

  • Remembers company context

    Profiles, product documents and presentation standards are loaded once and used in every session.

  • Executes through connected tools

    Chat, email, calendar, storage, spreadsheets and publishing channels.

  • Describe once, reuse without limits

    High-frequency, standardised work is handled at significantly lower cost and time.

Processing model

Analyses requests and makes decisions. Choosing the right model for each type of work is what determines operating cost.

Tool connection layer

Connections to chat, email, calendar, storage, spreadsheets and publishing channels. They define the scope of work the system can execute.

Context and background data

Company profile, product documents, report templates and presentation standards, loaded once and used from then on.

Training roadmap

Four sessions, 90 minutes each, one week apart.

Each session completes one deployment phase and ends with a component already running on the company's system.

01

Session 01 · 90 min

AI Agent foundations and setup on your own machine

Goal: Understand what AI Agents can and can't do, have a system running on your own device and define where it applies in the business.

  • Tell chatbots and AI Agents apart by context, tools and execution rights; the 4W + 1H framework
  • Install and configure the system on your machine and set a spending limit from day one
  • Run the first task on the company's real documents
  • Score repetitive work by frequency and standardisation, and pick the first three processes
  • Work that shouldn't be given to an AI Agent, and why
02

Session 02 · 90 min

Bring the AI Agent into the company's working channels

Goal: Move the control interface from the command line to the company chat and standardise how tasks are assigned so output quality is consistent.

  • Connect Telegram: a control channel, user limits, reading error logs; equivalents on Slack, Teams, Google Chat, Discord
  • Department-based workspaces, each with its own conventions for assigning work and formatting results
  • A five-part request standard: context, expected result, constraints, format, acceptance criteria
  • Load the company profile, product documents and presentation standards as shared context
  • Separate what the system handles alone from what needs approval before publishing
03

Session 03 · 90 min

Always-on infrastructure

Goal: The system runs independently of personal devices, with access control and a recovery plan for incidents.

  • Choose and configure a server and move the control channel from the personal machine to it
  • Manage access keys, firewalls, configuration backups and the version update process
  • Separate the test environment from production
  • Scheduled tasks: periodic reports, reminders, document roundups, content preparation
  • What to do when the system stops responding or returns poor results
04

Session 04 · 90 min

Operating costs and reusable assets

Goal: Make costs predictable and turn stable processes into assets the business owns.

  • A multi-provider model routing gateway with fallback if a provider fails
  • Allocate models across three types of work, track consumption and build a 12-month estimate
  • Package processes: standard requests, output templates, review criteria, approval rules
  • Document templates: reports, emails, proposals and presentation standards
  • Permissions for staff and a process list for the next 30 days

Training principle. From session 2 on, the participant operates the system directly while the trainer guides verbally. The business can maintain the system after the programme, without depending on a vendor.

Outcomes

By the end of the programme, participants gain six groups of capabilities.

01

Deploy and run the system

Install the AI Agent on a personal machine and a private server. Read error logs, restart services and update versions.

02

Operate through the company chat

Set up departments in the chat channel according to the org chart, assign work and receive results — no new software needed.

03

Write work requests to a standard

Write requests with enough information to get usable results the first time — a core skill independent of any tool.

04

Control operating costs

Understand the cost structure, choose models by type of work, set spending limits and apply optimisations.

05

Turn processes into assets

Package stable processes into report, email and proposal templates and presentation standards.

06

Choose the next process to automate

Classify work by frequency and standardisation to produce a prioritised list of next processes.

Who should join

A fit

  • Solo businesses, startups, small and medium businesses
  • People who run the business directly and know the internal processes
  • A significant volume of repetitive work: periodic reports, client emails, marketing content, capability profiles, customer care
  • Can set aside 2 to 3 hours a week between sessions to practise

 

Not a fit

  • Businesses without documented processes
  • People who fully delegate to staff and don't take part themselves
  • Organisations with multi-level tool approval processes
  • Businesses that want a fully outsourced deployment

How it runs

Three working phases.

  1. Week 0

    Preparation

    A 30-minute fit call, a short survey about size, tools and the three most time-consuming kinds of work. Then you receive a preparation checklist.

  2. Weeks 1 – 4

    Training

    Four private sessions, one a week. Between sessions there are exercises on real work and a dedicated support channel.

  3. 15 days

    Support

    A dedicated technical support channel after the last session, plus a 30-minute review to fix anything still unstable.

Programme fee

Contact

For one participant. Includes the intake assessment, four training sessions, the guide set and 15 days of technical support.

Book a 30-minute call
Third-party costs

Servers and AI models, paid by the business directly based on usage. The estimate is made in session 4.

Format

1:1 training, with content adapted to the business's industry and processes.

Payment

Two instalments: when the schedule is confirmed and after session 2.

Not included

General theory, multi-company classes, programming knowledge, turnkey deployment.

Frequently asked questions

What to be clear about before sending a request.

On the scope, way of working and responsibility limits of each service.

You can start from your goals, current process and the questions to decide. The scope is proposed after Auranium reviews the inputs.

No. The outputs can be used with your in-house team or another development partner, according to the agreed handover scope.

We can't confirm that before understanding the problem. The approach and scope depend on the questions to answer and the evidence available.

No. Consulting clarifies decisions and risks. Market demand still has to be validated with the right evidence.

Not by default. Prototypes, technical reviews or development are scoped separately if needed.

Auranium reviews the problem, outputs and responsibilities needed, then sends the scope and fee for your approval before starting.

Next step

Not sure which service to start with?

Clarify your current stage to choose the right kind of support instead of investing in the wrong direction.

  • Identify the problem to prioritise
  • Identify your current stage correctly
  • Choose the right starting step
Discuss your problem A direct conversation — no long documents to prepare.
Start your journey

Talk to us

We'll listen, ask the right questions, and tell you honestly if we're not the best choice for you.

Phone number

(+84) 094 4686 093

Zalo

(+84) 094 4686 093

Working hours

Mon-Sat (08:00 - 21:00)