Ahmed SolimanBrand & communication design

case study 03web app

Handit

A home for the small requests that get lost at work. Every ask gets one owner, one status, and a clean close.

the problem
Small requests at work get lost in Slack, email, and Teams, and people end up chasing each other with “any update?”
what I made
A web app that gives every ask one owner, one status, and a clean close, plus its name, logo, voice, website, manifesto, and pitch deck.
where it lives now
In private pilot. handit.to
The handit.to homepage: Every ask gets an owner, surrounded by stray requests like Who owns this? and Can legal review?

01in plain words

what it is

At work, the smallest requests cause the most chasing.

“Can you review this?” “Who can give me access?” “Can Finance approve the invoice?” Asks like these land in Slack, email, Teams, and texts. None of those tools was built to track them, so they scroll away. A few days later, someone writes, “Any update?”

Handit gives each ask a home. You drop it in one line. The right person accepts it. You can see where it stands without chasing, and when it’s done, it closes.

It’s small on purpose. Not chat, not email, not a project tool. Just asks.

Drop an ask in seconds: type the way you’d say it, and Handit lifts the owner and due date into chips, then lands the ask where someone can accept or claim it.
Type the ask the way you’d say it. Handit pulls out the owner and the due date, then lands it where someone can accept it.

02strategy

the strategy

Email is for correspondence.
Chat is for conversation.
Project tools are for projects.
The ask, “do this thing,” has no home.

The insight slide from my pitch deck, and the whole strategy in four lines.

  1. Own one thing.

    Handit handles the ask and refuses everything else: no projects, boards, threads, subtasks, or custom fields. The restraint is the product.

  2. Make ownership explicit.

    An ask isn’t real until its owner taps Accept. That one tap ends a classic mix-up at work: the sender thinks it’s handled, and the receiver thought it was a suggestion.

  3. Meet people where they work.

    Most asks are born in Slack, Teams, email, or a browser tab. So you can drop one from any of them without opening Handit.

  4. Sell to teams, not individuals.

    An ask needs someone on the other end, so Handit is sold by the seat and set up for the whole team on day one. Anyone can ask. Only the people who handle asks need a seat.

where it sits

Pitch deck slide: Everyone near this drifts. We hold the center. Please Do It became a chat app; Akiflow stays single-player; Halp and Assist are heavy ticketing; Handit is person-to-person, no chat, no overhead.

Every tool near this space owns one of Handit’s traits, then pairs it with the thing Handit leaves out. One went person-to-person but turned into chat. One is fast but single-player. One turns messages into requests but becomes a ticketing system.

Handit holds the center: person to person, no chat, no overhead.

how it reaches people

  1. Pilot inside one team.Start where the pain is real: one team, one workspace.
  2. Land 5 to 50 seats.A team lead can buy it on a card. No procurement.
  3. Spread across departments.Asks cross team lines, so adoption travels with them.

03words

the words

Handit is mostly language: a handful of plain words, used the same way everywhere.

the name

hand it → hand it off.

Handit is a verb you can already say: hand it. The brand line finishes the thought: hand it off. The pitch deck ends on it, the site’s last section says it, and the footer signs off with it.

five words, used everywhere

I gave every part of the product one short word, and used that same word in the code, the app, the website, and the pitch.

ask
the unit of work: one action, one person
wall
your queue of incoming asks
drop
the verb: hand it off
accept
the handshake that makes it yours
done
the only finish line

the headline, three tries

  1. May · pitch deckHand work off. Watch it get done.
  2. June · sales copyStop losing requests everywhere.
  3. now · handit.toEvery ask gets an owner.

The first described the action. The second named the pain. The one on the site makes a promise in five words, and it doubles as the product’s one rule.

words that close, not chat

  • The note field says Add a note…, not “Message.” Notes are capped at ten. It never becomes a chat.
  • The list of asks you’ve sent is labeled what your coworkers owe you.
  • When an ask lands on the wrong person: Wrong person? Hand it on, not back. And the rule behind it: One ask, one owner, never a chain.
  • Pricing in one line: Everyone can ask. Only handlers need a seat.
  • Sentence case everywhere. No Title Case, no ALL CAPS.
An ask packet: Jordan Blake asked you, accepted by you. A status track from Sent to Done, one clarify note, an Add a note field, and a Mark done button.
The ask packet: one request, one status track, a short note log.
Reroute: who should own this? A list of teammates with their teams.
Reroute hands the ask on, with a fresh accept.

the manifesto

“This is how a five-minute request becomes three days of coordination.”

“We were promised productivity. Instead, many people spend most of the day administering productivity.”

I wrote a manifesto for the long version of the why, and signed it as the founder.

The Handit manifesto page: What’s an ask? A unit of collaborative work deserves a home of its own.

the costly ask library

The costly ask library: The little asks with a real price. Can Legal sign off on the MSA before tomorrow? Kickoff slips, Sales chases Legal, revenue waits.

A library of 18 everyday asks, sorted by category. “Can Legal sign off on the Meridian MSA before tomorrow?” “Can IT give the new account manager access to Salesforce today?”

Each one shows what the wait costs in time, energy, and money, and how Handit closes it.

Browse the library

04design

the design

Calm, fast, and almost empty on purpose.

the mark

The Handit app icon: a white lowercase h, leaning forward, on a blue rounded tile
Handit lockup on light: blue h tile and the word handit Handit lockup on dark

A lowercase h, leaning forward, into the handoff.

It’s written, not drawn. The h in the icon and the h in the wordmark are the same letter, set in Manrope, all lowercase.

one color

One accent, one blue. Everything else is ink and paper. Green, amber, and red only ever mean a status.

  • blue#2F5BFF
  • ink#0D0E12
  • paper#F6F7F9
  • done#159A50
  • needs info#9A5B0B
  • blocked#D23B3B

the feel is the feature

The interface never waits on the network. Every tap lands instantly. There are no spinners and no “are you sure?” dialogs. You get five seconds to undo instead.

My test was a stopwatch: dropping an ask had to be faster than sending a Slack message.

Try the handshake:

Jordan Blake asked youForwarded · email · now
Sent

Turn around the contracting officer’s feedback before Friday.

A web version of the card, built from Handit’s own rules.

quiet by design

Sent: asks you’ve sent with statuses In progress, Accepted, Done, and a quiet outline label: Not seen yet

In the list of asks you’ve sent, an ask nobody has seen yet gets the quietest label, a thin outline, not the loudest.

Handit shows where things stand without nagging anyone. There are no “any update?” pings to send, because there’s nothing you need to ask.

the screens

The wall: incoming asks with Accept, Decline, and Needs info, and status labels like Accepted, In progress, and Needs info
The wall: everything asked of you, in one place.
Up for grabs: Casey Parker asked the team, with a Claim button
Don’t know who owns it? Put it up for grabs.
Sam asks from Slack with no seat; Maya accepts in Handit
Anyone can ask from Slack or Teams, no seat needed.

capture, wherever the ask is born

In Slack, a message’s More actions menu shows Send to Handit
Slack: “Send to Handit” on any message.
In Microsoft Teams, a message’s menu shows Send to Handit
Teams: same action, same wording.
Forwarding an email to ask@handit.to with the first line: @dana by Friday confirm these renewal terms
Email: forward it, write “@dana by Friday.”
A browser side panel titled Hand it off, attaching the current page to a new ask
Browser: hand off the page you’re on.

the website

Why Handit: Track it. Close it. A handoff inbox for unplanned work.
The handit.to homepage on a phone

The homepage lets you try the product without an account. “Why Handit” answers the buyer’s question: Track it. Close it.

the pitch deck

Thirteen slides, one idea each, in the same restrained style as the product.

Slide: An ask has nowhere to live. Slide: Three quiet taxes on every team. Slide: Email is for correspondence. Chat is for conversation. Project tools are for projects. The ask has no home. Slide: Handit gives the ask a home. Ask, wall, drop, done. Slide: Never open the app to send. Global hotkey, browser extension, Slack command. Slide: Demo-led. Land a team, grow the org. Slide: Make hand it off a verb.

05build

built, too

I wrote the build spec before any code existed.

It set the rules first: the vocabulary, the seven statuses, a list of features Handit must refuse, and the stopwatch test.

Then I built the web app to match, so every change shows up instantly, and added capture from Slack, Microsoft Teams, forwarded email, and a browser extension.

Handit is in private pilot. The offer is simple: bring one real handoff, and watch it close.

next

Proposal Hall