Our story.

Danny J. co-founded Vox & Loom with his brother, Victor, and leads the studio as CEO. His role is to turn a broad idea such as a site redesign or a better inquiry process into a project with clear priorities. That starts with understanding who the business serves, how customers reach it today, and where people tend to get stuck.

Danny leads discovery and helps define the scope, decisions, and handoff. He connects the work on the page with what happens inside the business: who answers a new inquiry, what information that person needs, and how the team will keep the site current after launch.

Victor J. is a co-founder and CTO of Vox & Loom. He leads technical direction across websites, workflow automation, and voice systems. His work begins with the systems a business already relies on, such as a booking calendar, a CRM, or a website editor, and considers what can be reused before anything new is added.

Victor helps the team map how data should move between systems, define what happens when an integration fails, and test the handoff from software to a person. He also plans for ownership after launch, including which settings clients can manage and which parts need ongoing technical support.

Godswill E. leads web design at Vox & Loom. He turns page goals, content, and brand direction into layouts that guide visitors from their first glance to the information or action they need. His scope includes visual hierarchy, typography, image direction, navigation, and the behavior of components on different screens.

He works with Emmanuel to translate designs into reusable components. Together they account for details that can get lost between a mockup and a build, such as long titles, keyboard focus, form errors, and how an editor can add content without breaking a layout.

Emmanuel C. leads web development at Vox & Loom. His role covers platform selection, implementation, and the editing experience clients use after handoff. Depending on scope, he builds page templates and content collections, connects forms or commerce tools, and checks how the result performs on common devices.

Before launch, Emmanuel follows the paths customers will actually take, including moving through the navigation, opening a project, and submitting an inquiry. He also documents the parts clients need to operate themselves, such as updating services, adding a project, or changing a call to action.

David E. designs the workflows behind Vox & Loom’s automation services. He starts by tracing how a task happens today: what starts it, which information matters, where decisions are made, and who owns the next step. That map helps identify the repetitive work worth automating first.

David’s scope includes lead routing, reminders, and follow-up sequences. He specifies when a rule can act automatically and when a person should review the result. He also considers missed events, duplicate submissions, and exceptions so the business can see what happened and recover when needed.

Michael U. leads voice solutions for Vox & Loom. He plans how an AI receptionist introduces itself, handles common questions, records messages, routes calls, and books appointments when a scheduling integration is in scope. The business’s own policies and approved answers shape each call flow.

Michael tests realistic calls with interruptions, incomplete information, or questions outside the approved knowledge base. He defines the point at which a caller should reach a person or leave a message, and helps the team review the call summaries it will use in day-to-day operations.

Habeeb manages projects and client success at Vox & Loom. He coordinates schedules, reviews, and approvals so clients know what needs their input and the delivery team can work from one set of decisions. His role covers the project from kickoff through handoff.

Habeeb tracks the details that can block progress, such as missing content, outstanding access, or a decision about scope. He helps prepare walkthroughs and handoff materials and makes it clear who owns the next action when an issue or a new request comes in.