DevZo.
WorkAboutContact
Start a Project
WorkAboutContactStart a Project

DevZo.

Founder-led studio in Karachi. We design AI assistants, automation, and custom applications. We show the work. We do not publish the client’s name.

Studio

About usWorkStart a ProjectCareers

Work

LumenMr AssistantHiring DeskNGO presence

Resources

JournalOpen rolesPrivacyTerms

Karachi

Pakistan

devzonaa@gmail.com

Mon to Fri, 10:00 to 18:00 PKT

© 2026 DevZo Studio. All rights reserved.

Karachi, Pakistan

Fintech/AI automation

Mr Assistant

Staff ask the organization once instead of pinging five people. Appointment requests go through the assistant.

Confidential commission. We describe the system. We do not name the organization or show their data.

Desktop assistant · Private corpus · Appointments

app.mrassistant.internal

Mr Assistant

Org knowledge

Rates

Contacts

Book

Ask the firm

Who handles FX onboarding, and can I book 20 minutes?
Treasury onboarding sits with the operations desk. Rate card is on the internal sheet. I can put 20 minutes on Thursday 11:00.
Appointment held · Thursday 11:00 · Operations
Ask about rates, owners, or book time

Result

Someone inside the firm can ask a normal question (who handles this, what we charge, what we offer) and get an answer from the organization’s own knowledge. If they need a meeting, they book it there.

The situation

Fintech teams run on specifics: products, rates, who owns which book, how a client gets on someone’s calendar. That material is written down somewhere and still asked out loud every day.

A public chatbot does not know the firm. A shared drive does not answer. They needed a personal bot for the company, trained on their world, not the internet.

Constraints

Answers had to be about this organization: contacts, rates, services. Generic finance advice was out of scope.

Booking had to live in the same conversation.

The company stays unnamed. No customer lists, no rate cards on this site.

Approach

A familiar chat in front of a corpus the firm already owns. Retrieval first: who-to-contact, rate, service. Then a composed answer.

When the intent is time with a person, the path switches to booking instead of inventing a calendar.

What we shipped

Chat trained on organization knowledge. Routing: whom to contact for what. Rates and services as the firm states them. Appointment booking from the same thread.

A desktop shell so it sits where people already work.

How it was built

A private knowledge layer, a conversational UI, and a booking action. We keep the model and store undescribed here so we do not sketch their security boundary.

What we’d do next

If they allow it: one anonymized question and answer on this page. Otherwise the story stays at the system level.

Start a ProjectAll work

More work

/01

Lumen

A closed platform that turns a one-line idea, or an existing website, into a working prototype, then into a handoff a team can build from.

Custom AI applicationsProduct teams

/02

Hiring Desk

A hiring CRM: a CV comes in, the system rates it, emails the candidate, and schedules the meeting.

AI automationHR / talent

/03

NGO presence

A public website that tells the story, takes an email, offers an appointment, writes to both sides, and stores the request in a database.

Custom applicationsNonprofit