Full-stack delivery grounded in real operations

We quickly understand the work behind your request and build the system it needs

We connect scattered work and repetitive tasks into one system,reducing processing time and missed handoffs.

Delivered cases

See how we solved problems close to your work

For confidential cases, we show the real business problem, design decisions, and implementation scope. You can also see how the work changed after delivery.

Delivered automation that turns ERP source text into quotes and client email drafts.

Before: Staff repeatedly read ERP text and wrote each quote and client email
Changed work: Quote writing and send prep continue in one flow; staff review content only.

View design and implementation

Judgment and design: We separated parsing, quote structure, and client wording rules, then defined human review points.
What we built: Built a tool that generates quotes and email drafts from ERP input and tuned it to their quoting flow.

Delivered automation connecting collection, evaluation, settlement, reports, and email for HR performance reporting.

Before: Evaluation data, settlement, reports, and email were handled across sheets and manual steps
Changed work: Repetitive aggregation and reporting are bundled while staff focus on exceptions and final review.

View design and implementation

Judgment and design: We defined collection, evaluation, settlement, reporting, and email stages with review checkpoints.
What we built: Implemented an Apps Script flow connecting collection, settlement, reports, and email templates.

Delivered a production tool that turns brand reputation data and scripts into repeatable ranking-style videos.

Before: Every ranking and trend update required another manual video edit
Changed work: The same ranking-style brand video can be regenerated by changing the data and script.

View design and implementation

Judgment and design: We separated scene structure, data binding, and render templates so the same format remains consistent as data changes.
What we built: Built a repeatable production pipeline combining Remotion scenes, render templates, and a generation CLI.

Delivered a tool that applies multiple pharma settlement rules with validation and report generation.

Before: Staff manually reconciled source sheets against a different rule set for each manufacturer
Changed work: Repeated cleanup, cross-checks, and report writing sit in one flow; staff handle exceptions only.

View design and implementation

Judgment and design: We separated settlement rules, validation steps, and output formats, then documented exception handling.
What we built: Built a desktop tool that reads source sheets and generates rule-based settlement, validation, and reports.

How we work

From inquiry through handover, we align on analysis, scope, design, build, and verification as needed.

Inquiry & work analysis

We map current workflows, repetition, bottlenecks, and tools in use.

Priorities & scope agreement

What to build first, completion criteria, and deliverables, aligned in writing.

Design & completion criteria

Screens, data, integrations, plus how we will verify behavior together.

Implementation & verification

Build the agreed scope and verify against real work scenarios.

Handover

Usage guidance and maintenance boundaries. Follow-up improvements as needed.

From web apps to internal systems

We design and build the interface, server, and data together.The items below are representative examples.The actual scope is shaped around your service and workflow.

Customer-facing web apps

Membership and sign-in flows
Booking and inquiry intake
Payment and content services

Internal work systems

Admin screens and dashboards
ERP, order, and settlement integrations
Document and report processing

AI and automation integrations

External APIs and AI models
Document and data extraction
Content and video production automation

More build cases

See more cases by domain in the public portfolio.

View full portfolio

FAQ

How do we define scope before a build starts?

We start with work analysis and agree on priorities, deliverables, and completion criteria. Analysis and scope alignment are part of the build process.

What happens after handover?

We walk through usage, maintenance boundaries, and how to verify behavior in daily work. Follow-up improvements can be discussed if needed.

Do you do web and app development?

Yes. As a full-stack developer, Lapin designs the customer interface, admin functions, server, and data together, adding automation and AI integrations when the service needs them.

How are cost and schedule determined?

By scope, number of integrations, data cleanup difficulty, and admin UI needs. We quote after reviewing your inquiry.

Can we combine corporate training?

Yes. Training and builds are separate scopes. We can discuss training followed by a build.

Corporate training (Korean) is available as a separate service.

What we need for a first conversation

✉ seonggyu@lapin.ai.kr

We quickly understand the work behind your request and build the system it needs

See how we solved problems close to your work

AI travel quote automation

HR and performance reporting automation

Brand reputation video automation

Pharma settlement automation

How we work

Inquiry & work analysis

Priorities & scope agreement

Design & completion criteria

Implementation & verification

Handover

From web apps to internal systems

Customer-facing web apps

Internal work systems

AI and automation integrations

More build cases

FAQ

AX consulting & build inquiry

What we need for a first conversation