LaneyLaney
← Careers

Laney story · Team and strategy

Not screens: we build the record and the action

What survives as AI erases software's screens, why Laney started in clinics, and how we plan to reach every offline business.

Our team

Plask, the company behind Laney, was founded in 2020 by three people who studied engineering at POSTECH. It began with NAVER D2SF's campus startup program in 2019; the AI we built after founding won a CES 2023 Innovation Award. We were named to Forbes Asia 100 to Watch, CEO Junho Lee and CPO Jaejun Yoo made Forbes 30 Under 30 Asia, and we spoke at NVIDIA GTC the same year.

Once the technology was recognized, we asked where it was needed most. The answer was the most complex operation in Korea: the clinic. To receive one patient, website, phone, messengers, booking books and ad tools run separately, and the front desk stitches them together by hand. Laney put all of it on one data model and passed 100 customers within 10 months of launch.

Laney is five people today. Five of us can serve 100 customers because we work with AI ourselves: the product, sales material, customer reports and this careers page are all built with AI. We use every day what we sell.

AI is erasing software's screens

For twenty years B2B software sold screens. People bought a CRM for its dashboards and pipeline views, priced per seat. Those screens made staff enter data, and muscle memory made switching hard.

Now AI agents read and write data directly, without screens. a16z calls it software "losing its head"; Salesforce launching a headless, API-first product is part of the same shift. Meanwhile anyone can build the tools they need with AI, and more companies cancel subscriptions saying "we can build this ourselves." Software that only sells screens and features gets harder to keep.

So what stays?

Both pieces land on the same answer: the screen may go, but these matter more.

  • The system of record: the one set of data a business trusts. The more agents there are, the more they need the same record.
  • Rules and permissions: the unwritten way a business works, plus which agent may do what on whose behalf, with an audit trail.
  • Owning the action: products that act, capture the outcome and use it to decide better next time.
  • Data the product creates: not imported data, but data that exists only because the product is in the loop.
  • The last mile in the real world: businesses tied to execution that won't be fully automated.
  • Buyers who can't build it: operationally complex businesses without engineers won't build and maintain this themselves.

And the software that survives doesn't tell customers to adapt to it. It becomes the base on which what each customer needs can be built quickly.

Where Laney stands

Laney is the customer record for offline businesses and the AI that works on top of it. Against the criteria above:

RecordCustomers, inquiries, consultations, bookings and visits live in one place; edit a treatment once and the website, AI consultations and reminders change together.
ActionThe AI answers an 11pm inquiry, books the visit, sends reminders and records the outcome. It works, not just watches.
New dataWhich questions led to bookings, which hours lose inquiries, whether an ad became a real visit: data that exists because Laney is in the loop.
Last mileTreatments, consultations and visits stay human and on site. Laney handles everything before and after so people can face the customer.
TrustClinics have the strictest privacy and medical rules. Enforcing who, and which AI, may see and do what is part of the product.
Hard to DIYClinics and shops have no engineering team, so FDPOs go on site and build what each needs on top of Laney.

Why we started with clinics

Clinics are the hardest test among offline businesses: high-value customers, long consultations, strict rules and many unwritten ones. If the record-and-action loop runs here, the same frame runs elsewhere.

After clinics: every offline business

The sign on the door differs; the frame is the same. Customers ask, consult, book, visit, pay and come back. Only each industry's rules and tone change: a dermatology treatment becomes a pilates class, a vet's vaccination cycle, a law firm's consultation slot.

Beauty and aesthetics, fitness and pilates, vets, academies, law and tax offices, auto repair, home services, lodging: every business that meets customers in person and runs on bookings has the same problem, complex operations and no engineers.

The steps ahead

  1. Deeper in clinics: close the loop from first inquiry through visit and return.
  2. More industries: keep the data frame, swap the rules, and move beyond clinics.
  3. A door for agents: prepare for customers' own AI assistants to ask and book through Laney, with Laney as the trust layer that decides and records what each agent may do.
  4. Network: benchmarks by industry and region and links between businesses, so each new business makes Laney more useful to the rest.
  5. Execution and payments: deposits, payments and dispatch, closing the loop into the real world.

Expansions we're thinking about

These are examples of directions we want to explore, not things we've built. In the FDPO assignment you can pick one or propose something better.

A new industryPick one industry, such as pilates, a vet or a law office, and make AI consultations and bookings run on its rules
Booking for agentsAn API or MCP endpoint where a customer's AI assistant can ask and book, with permissions and an audit trail
Calls to recordsTurn phone calls into customer records and next actions automatically
Rule extractionMine consultation logs for a business's unwritten rules (discounts, exceptions, order) and turn them into policies the AI follows
Run it by talkingA director changes prices, hours or copy in one sentence and the website and AI consultant update
No-shows and returnsPredict no-shows and prevent them with reminders or deposits, or bring customers back on their treatment cycle
Ad to visitAutomatically show how an ad turned into inquiries, bookings, visits and payments
Many locationsLet a franchise or multi-site HQ see every location's customer flow and push shared rules