# One by Lughlabs: AI teammates with their own computers

> One by Lughlabs is a platform for AI teammates that work on their own computers. An Architect maps how your business runs and designs a crew of specialized bots; you approve it before it’s built. Each bot works in the apps its job needs, from a catalogue of about 1,500, remembers what it learns, runs routines on a schedule and hands work to the next. Voice agents answer your phone line, and decisions that need you reach your phone. Bring your own model keys or use included credits. Creator is $40 a month or $240 a year; Business is $100 a month; Business Pro, on semi-private hardware, $400 or $1,000 as Business Max; Enterprise, a private server run for you, from $4,000. Lughlabs makes One.

URL: https://onedev.jobrella.ai/

## One handles every order while you cook with your family.

How it works

### One maps your entire business.

#### 01 Start with what you have.

Like a consultant, your Architect maps how your business runs and what matters most, then designs the crew to grow it. You approve it before it’s built.

#### 02 Bring or build your tools.

About 1,500 apps, connected once for the whole crew: some in one click, others with your own key. Missing one? Build your own with MCP or OpenAPI.

#### 03 Meet each bot at its desk.

Each one works on its own computer, in the apps its job needs. It tracks its numbers, runs its routines and passes work to the next. Correct it once and it remembers.

#### 04 Evolve with your Architect.

Your Architect sees every number and handoff across the crew, and keeps what the business learns. Each week it suggests what to improve, with its reasons, and changes only what you ask for or approve.

#### 05 Step away, stay in charge.

Routines keep their schedule and calls get answered. What needs your decision reaches your phone, and you settle it there. Back at your desk, everything the crew did is in Activity.

Product names and logos are trademarks of their respective owners. Their use does not imply endorsement.

Who it’s for

### What you’d hand off first.

Your business SaaS startup

#### Tickets answered before you’re in, the two that need you waiting.

Kai answers support from your help docs, Lena follows up demo requests, Ada answers security reviews and Nell drafts the investor update.

Your business SaaS startup Interactive example

Today

The crew takes first

- Answer this week’s tickets from the help docs
- Follow up everyone who filled in the demo form
- Answer a 60-question security review from your policies
- Draft this month’s investor update from the close

People

- **You** Founder

Crew

- **Kai** Customer support
- **Lena** Sales follow-ups
- **Ada** Security reviews
- **Nell** Books and investor updates

Works in

- Intercom
- HubSpot
- Gmail
- Google Docs
- Stripe

[One for Teams](https://onedev.jobrella.ai/one/teams) [One for Individuals](https://onedev.jobrella.ai/one/individuals)

An example. Every person and bot named here is fictional.

Features

### See what your crew can do.

Northline Studio is a fictional company for demo purposes. Every stage runs One’s own interface.

Inside One [Chapter 1: One mind](https://onedev.jobrella.ai/#intelligence) [Chapter 2: Voice](https://onedev.jobrella.ai/#voice) [Chapter 3: Computer](https://onedev.jobrella.ai/#computer) [Chapter 4: Routines](https://onedev.jobrella.ai/#routines) [Chapter 5: Self-evolve](https://onedev.jobrella.ai/#evolve) [Chapter 6: Build](https://onedev.jobrella.ai/#build) [Chapter 7: Made for you](https://onedev.jobrella.ai/#custom)

#### Your bots ask each other, share one Library and follow one Pulse. Brief one, and the crew moves.

Nora asks Maya whether the launch email can promise Saturday delivery. Maya asks Alex and Sage at once, Alex checks the studio’s shop, and Maya answers once, showing who helped and her sources. A café owner tells Sage on a call that cafés order the Ridge bowl in sets of 12; Nora keeps the fact, and Maya and Alex use it. On Pulse, wholesale enquiries rise from 3 to 11; the Architect brings the crew together in a group, and each bot takes its part.

#### Describe the phone agent you want. Your bot builds it, answers your calls and hands the work to the crew.

Nora asks Sage for a wholesale line. Sage builds a phone agent: its call flow from greeting to wrap-up, its voice from a description, a test call that passes, and the number, then asks Nora to publish it. Ana, who runs a café, calls the line: on her phone she asks for 24 Ridge bowls; inside One the live call shows her words and Sage’s, each step of the flow, the stock check and Nora’s calendar, where Sage books a call back for Tuesday at 10:30, and a text reaches Ana’s phone. When the call ends, Sage judges it against its criteria, writes a record to Enquiries and hands the work to Maya and Alex; Alex holds the bowls, and once Nora allows it, Maya emails the quote to Ana.

[Read the voice and phone guide](https://onedev.jobrella.ai/docs/voice)

#### Every bot has its own desktop, browser, terminal and files. It signs in and uses your apps the way you would.

Inside Alex’s own computer, full screen, with his cursor at work. He signs in to Stockyard, a wholesale marketplace, with a login Nora saved in One’s encrypted vault; Stockyard sends a sign-in request to Nora’s phone, she approves, and Alex’s browser stays signed in there, as it is to the studio’s shop, its mail and Kiln Supply. Asked to make the Ridge bowl €58 everywhere, he changes it in a spreadsheet, the shop and Stockyard, and checks all three in the terminal. Ordering glaze at Kiln Supply, he stops at the card field and asks for you; you take control, enter the card, hand back, and he places the order and saves the invoice to the shared folder. Then you show him how to export this week’s orders; he writes the steps down as a draft skill and repeats them in a test run.

#### Tell a bot what to do and when. It runs on a schedule, or the moment something happens.

Nora writes one sentence to Alex: every weekday at 7, send me yesterday’s orders and anything unusual. Alex turns it into a routine in his panel: its name, its instruction using the Weekly orders export skill, the schedule Weekdays at 7:00 AM with its cron line and its next runs, and Nora’s phone as where the result goes. The clock moves to Friday 7:00, the routine runs by itself, and Nora’s phone shows the result: 31 orders, €2,140, and six Ridge bowls to one café in Leeds. The next Tuesday, that café, Juniper Café, sends the wholesale form on the studio’s website; the form starts Sage’s routine at once. Sage reads it, looks the café up, and asks to call back, because a run started by a webhook asks before a call; Nora allows it, the café’s phone rings, and Sage writes a record and hands the price list to Maya, three minutes after the form. Then the crew’s week, as a lane for each bot from Monday to Monday: every scheduled run, the form, an email, and Ridge bowl stock falling under 10, each lighting up as the week passes; you can move through the week with a slider. On Monday at 8:00 Maya’s weekly brief asks Alex and Sage for their parts and sends one file to Nora’s phone. Last, Alex’s runs this week, as a record: what started each, how long it took and what it made; Tuesday’s Stockyard sync failed because the sign-in had expired, and recovered after Nora approved signing in again; Nora opens Wednesday’s Morning orders to see its steps.

[See routines in operations](https://onedev.jobrella.ai/use-cases/operations)

#### Each bot tracks your outcomes and tests what moves them. Your Architect turns what they learn into your next strategy.

Twelve weeks into Northline’s fictional One. Maya’s Analysis shows the numbers she is judged on, each with its source, her chart with every version of her playbook, and her reading: subject lines that name a piece seem to get more opens. She tests it on 10% of the list: two subject lines, two inboxes, 41% against 29%. She sends the winner to everyone, moves her playbook to v5, Nora keeps the lesson in the Library, and the list’s line bends up. On Pulse, the Architect reads that wholesale has tripled in four weeks while retail is level, and drafts strategy v6: lead with wholesale, new work for Maya, Alex and Sage, a routine and a target. Those apply at once, as Nora set it; a new bot, Hollis, waits for her. History shows twelve weeks of changes and what each one moved, including one reverted and one stopped by its guardrail.

#### Bots write the tools they need. Your engineer bot builds your sites and apps, publishes them and keeps them running.

Alex has compared three kiln suppliers’ price lists by hand three weeks running, so he writes a script on his own computer, installs what it needs, tests it against last week’s lists and saves it as a skill, Supplier check; he uses it at once, and typing / in the composer lists it with the space’s other skills. Remy, the crew’s new engineer bot, builds a wholesale portal from one message: a plan (pages, data, trade prices from the Library, sign-in by email link), files and code on its own computer, an orders table, passing tests, and a preview that assembles beside the code; Nora comments on the preview’s button and Remy changes it. Nora publishes the first release to the studio’s own address, wholesale.northline.example; outside One, Juniper Café signs in and orders two sets of 12 Ridge bowls, and the order comes back into One as a record, with handoffs to Maya to confirm it and Alex to hold the stock, and a skill that lets the crew look orders up. When checkout fails, Remy reads the logs, finds that VAT is not rounded to the cent, writes a two-line fix with a test, and asks Nora on her phone to publish version 1.0.1; she does, and checkout errors return to zero.

#### Business, Company and Enterprise customers can ask us for a custom feature or workflow. We agree the scope, feasibility and plan together.

Northline Studio’s One has Kiln, a feature made for the studio. Beside the iPad stands the studio’s kiln controller, and its readings travel into Kiln, which shows tonight’s glaze firing: its program, its temperature curve as it rises, and what is in the kiln. Alex plans stock around it: 24 Ridge bowls out of the kiln on Thursday, so wholesale can ship on Friday. Maya drafts the journal line, Fresh from the kiln on Thursday. Then a routine only Northline could have: when a firing finishes, tell Nora and update stock. Then how it came to be: Nora asks the One team for her kiln in One; the scope and then the plan are agreed together; it is built, the controller is connected, and Kiln arrives in her sidebar, where Alex uses it first.

[Ask for a custom solution](https://onedev.jobrella.ai/contact?interest=Custom+solution) [Create your One account](https://one.onedev.jobrella.ai/sign-up) [One on a private server](https://onedev.jobrella.ai/one/enterprise)