SMS Booking Router
Leads asked the same questions about services and prices, and every reply was typed by hand. Two SMS flows now answer, branch on the choice and tag the contact for booking.
Walkthrough on requestA small senior team building AI agents, automations and integrations for startups and growing businesses. You work directly with the engineers who build your system.
Built with the tools your team already uses
We're a small team of senior engineers. The people on your first call are the people who build your system, and they stay to run it. No account managers and no hand-offs.
Five things we build for clients, and keep running after launch.
Agents that answer questions from your database, triage support tickets, read contracts and sort shared inboxes. They read and draft. A person approves anything that gets sent, booked or changed.
Claude · OpenAI · Python · Postgres
Lead follow-ups, payment flows, client onboarding and reminders, built in GoHighLevel, Make, n8n or Zapier. Every flow gets an alert and a log, so a failure never goes unnoticed.
GoHighLevel · Make · n8n · Zapier
Stripe, your CRM and Odoo connected, so a won deal creates the order, the invoice and the fulfilment task from one record. No CSV exports and no re-typing between teams.
Stripe · Odoo · GoHighLevel · APIs and webhooks
Dashboards, portals and internal tools for the jobs off-the-shelf software doesn't cover. The code lives in your repository from day one.
Next.js · Node · Python · Postgres
After launch we monitor, fix and improve what we built, and send a short monthly note on what changed.
From $600 a month
Four builds for clients. We keep clients anonymous unless they've agreed to be named, and we'll walk you through any of these on a call.
Leads asked the same questions about services and prices, and every reply was typed by hand. Two SMS flows now answer, branch on the choice and tag the contact for booking.
Walkthrough on requestOnboarding depended on someone remembering to send emails and chase documents. Now a portal flags missing items, chasers list exactly what's missing, and reminders run until the call is booked.
Walkthrough on requestOrders arrived on the website while stock, invoicing and delivery lived in the back office. Every order now lands in Odoo as a sales order, with nothing re-typed.
Watch the walkthroughSales and finance worked from different records, so every closed deal meant entering the same details twice. A won deal now sets the whole operational side moving.
Watch the walkthroughEach one is a working build, shown here on sample data for a fictional home-services company. We adapt them to your database, help desk, inbox, calendar, Jira and HR tools.
Plain-English questions become one read-only SQL query, a chart and a short answer.
Read-only access. Every number is checked against the query result.
Reads a ticket, checks bookings, texts and policy, finds the root cause and drafts the reply.
The reply and any action wait for a person to approve.
Key terms, deadlines and risks from a contract, and answers with exact quotes.
Every quote is checked word for word. Deadlines are calculated in code.
A technician's rough notes become a customer-ready report with a priced quote.
Prices only from your price list. Measurements checked against the notes.
Finds times across people and time zones, and drafts the invite.
Every option is rechecked against the calendars. Nothing is booked without a person.
Sorts a shared inbox by urgency, lists who does what by when, and flags phishing.
It never sends. Drafted replies wait for a person to edit and send.
Sprint risk, blockers and the stakeholder update, from the team's Jira data.
Points, pace and blockers are computed in code, not estimated by the model.
Employee questions answered from the handbook and their own record, with citations.
Sees only the signed-in employee's record. Sensitive topics go straight to HR.
Agents read and draft. People approve. Nothing is sent, booked or changed on its own.
Working with an offshore team should feel like working with the team down the hall. These are the commitments in every contract.
A standard services agreement and NDA, signed before any technical work starts.
It lives in your repository and accounts from day one, and it's yours once paid.
A fixed price per sprint or milestone. Hourly work is capped each week, with timesheets every Friday.
We bill per milestone, so you never prepay more than two weeks of work.
We work with access you grant and can revoke at any time, and we tell you which AI service sees which data.
Every delivery comes with documentation, a handover call and 30 days of free fixes.
Most clients start with a sprint or a proof of concept, then move to delivery and monthly support. Each step is small enough to say yes to.
A clear plan, tool choices, estimate and risks, whether or not you hire us to build it.
$500fixed
The riskiest part built and working on your data, before you commit to the full project.
From $1,500fixed
Design, build, test, deploy and hand over, in two-week milestones you review.
$25/hror a fixed price per milestone
A senior engineer on your team, in your tools and standups.
$25/hr20 to 40 hours a week
After launch, Run & Support covers monitoring, fixes and monthly improvements, from $600 a month.
30 minutes, free, with the engineers who would build it. Bring one workflow or one idea.
Within a day: the approach we'd take, the risks, and a rough estimate.
A fixed price for the first step, a sprint or a proof of concept, for you to review at your own pace.
Prefer LinkedIn? Message us at linkedin.com/company/lumously.