The case for a keyboard-first phone
Watch someone work fast for a few minutes and you'll notice their hands barely leave the keyboard. They tab between windows, fire off shortcuts, search instead of scroll. The mouse is a last resort, reached for only when nothing else will do. That instinct runs through every tool they use all day, with one strange exception: the phone. This is the case for a keyboard-first phone, and why business communication is the last place on your desk the keyboard never reached.
A keyboard-first phone lets you reach anyone without touching the mouse or switching apps. You summon it with one keystroke from inside whatever you're working in, type a name, then press enter to call or shift-enter to message. No hunting through contacts, no app to find first. The point is the distance: from the thought to the conversation in about a second.
Why power users treat the mouse as a last resort
The keyboard is faster, but that's not really why. It's that the keyboard keeps you where you are. Your eyes stay on the work, your train of thought stays intact, and the next action happens without a context switch.
Every reach for the mouse breaks that. You leave the keyboard, hunt for a cursor, aim, click, come back. It takes a second or two and it costs more than a second or two, because you've stepped out of the flow you were in. It's a small tax on attention, paid dozens of times a day.
Here's the part that matters for a phone. That break is where most communication hesitation lives. The message you meant to send but didn't. The quick call you put off because reaching for it felt like a detour. The biggest cost in a small business isn't the conversations that go badly. It's the ones that quietly never happen.
Keyboard-first has already won everywhere except your phone
Look at the tools serious users reach for and the pattern is everywhere. The browser search bar. The terminal and the command line. Keyboard shortcuts in Excel, Photoshop and Final Cut. A whole generation of modern software, Raycast, Superhuman, Linear, built on the same three ideas: a global hotkey to summon it, a command palette to drive it, and a shortcut for every action so your hands never leave home.
These tools share a temperature. They're minimal, considered, and they sit at the edge of your focus, resident but not intrusive, until you call them forward. They're not Olatti's competitors. They're its peers, and they set the bar.
Business communication never caught up. Teams and Slack still make you click. RingCentral and Dialpad still make you navigate. Zoom Phone still makes you wait. The category was built for IT procurement and feature-checkbox parity, not for the person actually using it all day. As I sometimes put it, Teams is a Swiss army knife. We're trying to build a samurai blade.
You feel the difference in the small things. Dial out on Teams and you'll often sit through about ten seconds of a strange bubbly noise before the call even connects. That's not a bug. That's a product built for a buyer who'll never have to live with it.
How long should it take to reach a colleague?
Today, even in a keyboard-optimised flow, reaching a colleague takes roughly three seconds: summon the app, type the name, pick from a list, press call. Three seconds doesn't sound like much. But it's not the seconds, it's the break, repeated all day.
Voice assistants are slower, not faster. In our own testing, asking Siri or Google to place a call takes nine to eleven seconds, and they don't prioritise your work contacts or stay in the app you wanted. They were built to answer the weather, not to reach Tom in accounts.
The bar we build Olatti to is about a second and a half, from any window you happen to be in to a message sent. That's a founder's claim against a keyboard demo, not a lab number, but it's the target the whole product is measured against. Once reaching someone is that cheap, the hesitation disappears, because the cost of acting drops below the cost of not acting.
What a keyboard-enabled phone actually does
It comes down to one gesture. Double-tap to summon Olatti from inside any app, a CRM, a spreadsheet, Figma, a browser tab, a terminal. The work stays exactly where it is. Type a name. Press enter to call, shift-enter to message. No mouse, no app-switching, no scrolling through contacts. The shortest possible distance between the thought and the conversation.
The rest of the time, it's out of the way. Olatti is loaded and one keystroke away, but it lives behind your work, not in front of it. It doesn't beg for attention with badges and popups. You reach for it because it earns the reach, not because it's nagging you.
Building around the keyboard also changes what you build, and what you refuse to build. Most chat tools give you three things: direct messages, group messages and channels. But a group message is just a channel without a name. So we removed the middle one and let you name it instead. That's the discipline in one example. Removing friction isn't adding a setting. It's removing a whole category, so there's one less decision to hold in your head. There's more on why we built Olatti this way if you want the longer version.
The phone is overdue
The keyboard already won the rest of your desk. Your editor, your spreadsheet, your search bar, your terminal, all of it bends to your hands and gets out of the way. The phone is the one tool that still makes you stop, click and wait. There's no good reason for that anymore.
A keyboard-enabled phone is just the same idea, finally applied to the thing you do most: reaching people. Communication at the speed of thought, so you can stop managing the tool and just have the conversation.
That's what we're building. You can see how Olatti works, and if it's the business phone you've been quietly waiting for, join the waitlist and we'll keep you posted.