How we work

Turn shared knowledge into a change in daily work

Your team brings the operational context and decision rules. Roundin builds the structure that connects them to execution. Together, we check whether the system supports the work and the business outcomes that matter.

Download company overview PDFKorean

Our process

01
Find the knowledge
Agree the first task, implementation scope and baseline for comparison.
First workflow and scope
02
Connect the knowledge
Define exceptions, approvals, access and who maintains the information.
Knowledge and approval flow
03
Apply it to work
Staff test representative tasks and review accuracy, usability and changes needed.
Working screens and files
04
Review and extend
Agree ownership, support, improvement priorities and whether to expand.
Validation and operating criteria

What your team receives

Operational knowledge with rules and sources

A connected structure of company terms, materials and workflow rules, with references. Staff can use the same basis when a new task arrives or responsibilities change, and designated owners can maintain the information.

Operational knowledge structure example

Interfaces your team uses in daily work

Screens for the agreed tasks, such as document preparation, booking management and change review. Staff can see related materials and progress together, identify exceptions and approvals, and carry out follow-up.

Built interface · Unified booking list

Documents and data ready for review and use

Documents in company formats, editable files, structured data and change history. Staff can review and revise the content before sharing it with customers or using it in the next proposal or change request.

Sample output · Quotation

Criteria for evaluating and operating the system

Before-and-after records, user guidance, access responsibilities and information-update and incident procedures. The team knows who manages what, how issues are handled and which improvements to make next.

Operating guidance example

Common questions

Do you work only in certain industries?

We work across industries.
Travel and leisure are the projects we currently share publicly.
For a new domain, we review the team's work and materials to understand its rules, exceptions and system constraints before agreeing scope.

How is the project scope decided?

We define the workflow to improve, expected outcomes and acceptance criteria alongside the functions to build.
We choose the appropriate combination of simpler processes, rule-based automation and AI.
Ongoing support and further improvements are agreed separately.

What will our team receive?

Depending on the agreed scope, you receive working interfaces, documents and data outputs, validation criteria and findings, and operating and handover guidance.
The contract specifies code and data handover, connections to existing systems and support responsibilities.

How do you assess results and cost?

We agree comparable measures such as processing time, corrections and omissions, review workload and operating cost.
After evaluating the initial implementation, we decide whether to expand.
Pricing depends on system connections, data readiness and operating requirements.

How are client data and AI decisions handled?

We agree the data and access needed, what may be sent to external models, and retention requirements in advance.
Decisions such as pricing and sending documents externally include staff review or approval.
Sensitive source materials are shared through a separately agreed channel, rather than the contact form.

Tell us about your team's work

We start by listening to the people who do the work