The Medical Engineers

01  /  work

These are two builds you can open in a tab.

Most of what we run sits inside somebody else’s systems and cannot be shown to you: an automation does not photograph well and a chart integration is nobody’s to publish. These two are public end to end, so you can check every claim on this page against the live site.

02  /  case studies

This is what was built, and what it does now.

Each one is the same shape: the problem, the build, how it gets found, what it measures, and what stopped being somebody’s job afterwards.

01

MVM Heart, Vein and Vascular CentersIt is a cardiology and vascular practice in South Florida.

mvmcardio.com

This was the brief.

The client is a two-location heart, vein and vascular practice with five pages of website and a great deal more than five pages of medicine. Patients arrive searching a condition, not a practice name, and referring physicians arrive wanting to know what is treated and how fast someone is seen. Neither had anywhere to land.

This is what we built.

It was a full rebuild, from five pages to twenty-nine. It has service lines for vein and vascular, cardiology, limb preservation and diagnostics, and a condition library covering peripheral artery disease, critical limb ischemia, carotid disease, aortic aneurysm, varicose veins, deep vein thrombosis, vascular ulcers, coronary artery disease, heart failure, hypertension and atrial fibrillation. It has clinician pages, two location pages, an insurance page listing what is accepted, downloadable forms, a route built for referring physicians, and a full Spanish site rather than a translate button, which is a build decision as much as an editorial one: two language trees, declared to the search engines as variants of each other.

This is who wrote it.

The copy is the division’s marketing company’s, written for patients rather than for other clinicians. We built, structured and instrumented the site around it. We are telling you which half was ours because a firm that claims both usually did neither well.

This is where patient data stays.

It stays in the practice’s own chart. The portal and scheduling are the chart’s, linked rather than rebuilt, which is the same answer we give every practice that asks us for a portal of their own.

It is found by people and by machines.

Each condition answers its question in the first screen, in the words a patient would type, which is also what an AI assistant needs in order to quote the practice correctly rather than paraphrase a competitor. The organization, the clinicians, the locations and the services are described in machine-readable form. English and Spanish are declared as language variants so they rank together instead of competing, the site is verified with the search engines and its sitemap submitted, and indexing and query performance are watched after launch rather than only at it.

It was measured, then advertised.

Conversion tracking was wired in at build time, in the practice’s own accounts, so an appointment request is a number rather than a guess, and campaign spend can be judged on booked consultations instead of clicks.

It is automated into the practice.

Inquiries, forms and physician referrals do not sit in an inbox. They are routed to the right location, acknowledged, assigned and tracked in the systems the team already works in, so the front desk works one queue rather than checking several.

What was the scope?

It went from 5 pages to 29.

Where are the locations?

They are in Miami (Kendall) and Homestead.

What languages does it have?

It has English and Spanish.

What is the platform?

It is WordPress with a custom theme.

02

The D&M Emerging Artist AwardsIt is a national open call and live production in Dallas.

dmhalloween.com

This was the brief.

The client is a charitable foundation running a national open call for emerging choreographers, with an immersive production in Dallas on October 31 and a hard application deadline. There was no site, and nothing else existed either: the call, the referral program, the prize terms and the press material all had to exist in one place before artists could be asked to apply.

This is what we built.

It is a new site, video-led on the home page and plain everywhere it matters. It covers the awards and their terms, the production, the scout program and its referral fee, the application route, a gallery, press, and a list for people who arrive after the deadline and want to hear about the next call.

It was built around a date.

An open call is built around a deadline. The application window opens and closes on fixed dates, and the site shows correctly which side of that date it is on without anyone editing a page at midnight.

It is found by people and by machines.

The terms, the dates, the eligibility and the prize amounts are stated as facts on the page, which is what makes an assistant asked “how do I apply” answer with the foundation’s own terms. Share cards were built so a link dropped into a dance department or a group chat arrives as an invitation rather than a URL, and the site is verified with the search engines and its indexing monitored through the application window, when it mattered.

It was measured, then advertised.

Tracking was in place before the call opened, in the foundation’s own accounts, so paid reach could be judged on completed applications rather than impressions, and turned off once the window closed.

It is automated into the foundation.

Applications and referrals arrive in one reviewable pipeline with their source attached, so a scout can be credited for the artist they sent, acknowledgements go out on their own, and the shortlist is notified from the same place the applications landed.

What was the starting point?

There was no existing site.

When is the event?

It is on October 31 in Dallas.

What was it built for?

It was built for a fixed application window.

What is the platform?

It is WordPress with a custom theme.

03  /  what a build includes

A site is not finished when it looks finished.

Four things decide whether a build does its job, and none of them are visible in a design review.

It is found by people.

That means structure, speed and plain semantics, internal links that follow how somebody reads, a sitemap submitted and the site verified with the search engines. Then comes the part most builds skip: indexing and query performance are watched for the months after launch, because that is when what you assumed about your own patients turns out to be wrong.

It is found by machines.

A growing share of first contact is now an assistant answering on your behalf. It answers well from pages that state facts plainly, answer the question in the opening lines, and describe the organization, its services, its locations and its people in machine-readable form. Do that and the answer given about you is yours and current. Skip it and the answer is assembled from whoever did.

It is measured, then advertised.

Conversion tracking is wired in during the build, not bolted on when the first campaign underperforms, and it lives in your accounts under your billing. Once an inquiry, a booking or an application is a number, advertising can be judged on the thing you wanted rather than on traffic.

It is automated into the organization.

A form that lands in an inbox has created work, not removed it. What arrives should be routed to the right person or location, acknowledged, assigned, tracked and reportable inside the systems your team already opens every morning. That is the difference between a website that creates work and one that removes it.

04  /  platforms

We build custom when it is justified, and on a platform when it is not.

We build custom, and we build on WordPress, Wix, Shopify and the rest. The choice is an engineering decision, and we will argue for the cheaper one when it is the right one.

A platform is right for some sites.

It is right when the site is content and commerce, the team will edit it weekly without calling anyone, and nothing it does has to reach into a system of record. You get a lower bill, a lower ceiling and an editor your front desk can use. Both sites above are built this way, and both of them should be.

Custom is right for others.

It is right when the site touches intake, scheduling, eligibility or a chart, when the logic is yours rather than a plugin’s, or when what you are building is closer to an application than a brochure. It costs more to build and less to live with, and we will tell you which side of that line you are on before you have paid us anything.

Either way, it is yours.

The domain, the hosting, the accounts, the tracking and the repository are in your name and billed to you from the first day. Leaving us is a password change, not a migration project.

No client work appears on this site without permission, and nothing here is a reconstruction. If a number on this page cannot be checked against the live site, it came from the client and they can confirm it.

05  /  next

Ask what it would take.

Bring the site you have, or the date you are working toward. The first conversation is about what has to happen, not about a stack.

Start a project

06  /  contact

Get in touch.

Tell us what the site has to do. If a platform gets you there for less, we will say so.

// We use this only to answer you, and we never share it.
// Do not send credentials, PHI or production data through this form.

Dubai

Meydan Free Zone
Dubai, United Arab Emirates

United States

Spring City, PA 19475
United States