BUSINESS SYSTEMS FOR SMALL TEAMS

Your team’s next step.
Not another question for you.

Less chasing, searching, and asking you what comes next. I connect your company’s knowledge, tools, and workflows into one operating system, with important decisions ready for your review.

Discuss your workflow ↗See how it works ↓

Soju LeeFrom understanding the work to building the system.

PUBLIC DEMO · COMPANY OPERATIONS SYSTEM

Connect calls, email, messages and company knowledge in one operating flow.

Illustrative operating flow

Requests arrive

Work from several channels comes together.

The owner reviews the next actionQuote request · past quote · company ruleAwaiting approval

A 3D work flow connecting calls, email and messages to company knowledge and owner approval. Work from several channels comes together.

CONNECTED TO YOUR TOOLS·BUILT AROUND YOUR RULES·PEOPLE STAY IN CONTROL

01 / WORKFLOWS WE CAN CONNECT

From a request to the next action.

What comes in, what informs the decision, and who approves it. Follow one workflow through.

A call on the road. A quote ready to review.

Connect the request from a call, the specs in an email, and the terms from a previous quote.

01Intake
02Link evidence
03Review
04Dashboard

Inbox3 related records

↗Call record01

“Could you quote for 5,000 bags like last time? I’ll email the specs.”

@Specification email02

PE 300 × 400 mm. Please confirm thickness and lead time.

···Message confirmation03

“I’ve sent the email. Let me know when the quote is ready.”

COMPANY CONTEXT

Match product and dimensions to the previous quote
Check specifications and calculation rules
Flag thickness and lead time for a person to confirm

Your reviewCollecting evidence

A NEXT STEP, WITH EVIDENCE

Prepare a PE bag quote

Item: PE · 300 × 400 mm
Quote quantity: 5,000 bags
Before execution: Confirm thickness and lead time before sending

Connect the records to review a proposal alongside its evidence.

DASHBOARD

The decisions that need you.

→

Your reviewed work continues here.

Keep the next steps in view, with more room for decisions and relationships.

A recreated workflow example. No real customer data is used and no quotes, orders, or messages are sent.

THE SAME PATTERN, ACROSS YOUR OPERATIONS

Orders → productionPurchasing → receivingDispatch → paperworkPayment records → follow-up

02 / A CASE STUDY FROM THE FAMILY BUSINESS

Built around a real person’s working day.

Remembering a call. Sending a quote away from the desk. These tools started with small, specific requests from my dad.

CALL → DESKTOP▤Call summary.pdf

Who · What · What’s next

ONE FILE TO FIND

01 / Recreated output

BUILT & USED

When the call ends,
the context stays.

Follow-ups could slip between a call on the road and getting back to the office. I built a flow that relays recordings, transcribes and summarises them, and saves the result on Dad’s PC.

My contribution & what changed +

Android upload → VPS relay → processing on Dad’s PC → speaker-aware transcription and summary → PDF. I separated internal processing files from the one final PDF he needs to find. Uncertain names and speakers remain reviewable. Console windows interrupting his work also taught me to design for the working day, not just the output.

Successful processing results and PDFs have been verified. I haven’t measured a reliable accuracy or missed-call rate yet.

Read the build note ↗

HANAFILM / RECREATED QUOTE FLOW

A quote. Within reach.

PE FILM300 × 400

QUANTITY5,000

Create → Save → Reopen → Share

02 / Example, not customer data

BUILT & USED

A quote shouldn’t have
to wait for a desk.

Dad wanted to send his Excel-based quotes from his phone. I turned that workflow into a web app, keeping the working rules and saving quotes on the server so they can be reopened.

Turning working rules into a product +

I worked through the specifications, calculations, editing, saving, versions, and image-sharing flow. Preserving the existing calculations mattered as much as the new interface. Usage and implementation are documented; sharing and receipt haven’t been verified on every device.

Read the build note ↗

INTEGRATED INBOX

Separate records. One working context.

I built an integrated AIOS inbox that brings records from calls, email, messages, and files together for review. It keeps the source attached and connects related work, so the next item to check is easier to find.

CallsEmailMessagesFiles↓ Review inbox

Scope and next steps +

A multi-source inbox output has been verified. Live coverage varies by channel; the quote recommendations, purchasing, and staffing examples above illustrate possible applications. The aim is less repetitive admin and more room for relationships and important decisions.

03 / MY DAD MAKES PLASTIC BAG

If Dad couldn’t pick up
for a week?

What stayed with me wasn’t how much he did. It was how hard it was for him to step away.

An illustrated owner reviewing organised work on a phone — Illustration inspired by the case study · not a portrait of my dad

Helping at the family factory, I saw calls taken on the road, quotes waiting to be sent, and requests waiting for a reply. So much of the work depended on one person remembering it all.

“It would help if my calls were written down.”

That was the starting point: a record he could find when he needed it, and a next step he wouldn’t have to keep in his head. That request led to call records, a mobile quote app, and an integrated inbox.

Read the original field note ↗

04 / HOW WE WORK TOGETHER