Penthoria Digital · Washington, DC
About the firm
Who you would be working with
The people and principles behind the work
Penthoria Digital is a consulting and digital delivery firm based in Washington, DC. We are deliberately small. The person who scopes your engagement is involved in delivering it, which is the main reason clients choose a firm our size over a larger one.
This page covers who we are, how we make decisions, and the limits we work within. If you want the practical version first, start with how we work; if you already know the shape of your project, book a consultation and we will tell you early whether we are the right fit.
Column 01
One engagement holds strategy and delivery. The deck and the build are the same idea.
Most engagements run remotely with U.S. clients, and we meet in person around the DC metro area when a room full of people beats a call.
Column 02
We are not a fit for every project, and we say so early.
Firms wanting the lowest-cost template build will find better options elsewhere. We would rather point you there in week one than bill you through month three.
Column 03
1201 Market Street, Suite 1500, Philadelphia, PA 19107.
Monday to Friday, 9:00 AM – 6:00 PM Eastern Time. Consultations are booked through the contact page.
Column 04
Case studies, process notes, and pricing logic we are willing to put in writing before you sign anything. Nothing about the firm is kept back for the sales call.
Origins
Why the firm exists
The gap we kept running into is the one between strategy and build. A company hires a consultant who produces a deck, then hires a developer who builds something else, and the deck goes in a drawer.
We started Penthoria Digital to close that seam. Strategy and delivery sit in one engagement, so the recommendation and the thing that launches are the same idea. It sounds obvious. It is surprisingly rare in practice.
That structure also means we turn down work where the two halves do not belong together — a quick template build with no strategy behind it, or a strategy engagement where nobody is going to ship anything. Saying no early is cheaper for both sides than discovering the mismatch in month two.
Team
Who you would be working with
You would be working with a small team of strategists and builders, not a rotating bench of contractors. The delivery lead you meet at kickoff stays through handover — the name on the proposal is the name still answering email the week you go live.
We are based in DC and most engagements are with U.S. clients, run remotely with in-person meetings when they are useful in the metro area. Beyond that, we hire for judgment, not for headcount, and we keep the roster small enough that nobody is a stranger to the project.
Column 01
Strategy and delivery on the same team
The person who scopes the engagement is involved in delivering it. No handoff to a bench of strangers, no second interpreter of your brief.
Kickoff to handover
Column 02
One documented contact, introduced in writing
You get an email address and a phone number for the delivery lead, not a shared support inbox. Questions land on a real person who has read your file.
Named in writing
Column 03
Small enough to fit, large enough to deliver
Two to four people on a typical engagement, which keeps decisions fast. When a build needs more hands, we bring them in on the same standard, not on a separate team charter.
2–4 on a team
Column 04
Remote first, in person when it counts
Most meetings are calls. Kickoffs, workshops, and final walkthroughs can be in person across the DC metro area when a room would move the work forward faster.
DC metro area
Projects fail from unclear boundaries more often than from bad work.
So every proposal we send has an exclusion list on it. What is out of scope, said plainly and in writing, before the work starts.
Method
How we make recommendations
We start from what your data says, not from what is fashionable. That means looking at your actual traffic and conversion numbers before proposing a rebuild, and occasionally telling a client that the site is not the problem.
We also name the constraint out loud. Budget, timeline, internal capacity, and legal requirements all shape what is realistic, and pretending otherwise wastes everyone's first month. Where two approaches would both work, you get both with the tradeoffs spelled out rather than a nudge toward the pricier one.
Step 01 · Diagnose
Read the numbers first
Before we propose anything, we look at how your site actually performs: where visits come from, which pages hold attention, and where people leave. A rebuild is one answer among several, and it is not always the right one.
Step 02 · Name it
State the constraint
Budget, deadline, and internal capacity get written into the plan instead of assumed. What is realistic changes once those are on the table.
Step 03
Compare
Both routes, side by side.
Step 04 · Propose
Written scope
You receive a plan with inclusions, exclusions, and the measure we will report against. Two clicks on the same document is the default, not a special request.
Step 05 · Build
Deliver in one lane
The same team writes, wires, and reviews. Handoffs inside the firm are one conversation, not a ticket queue.
Step 06 · Hand over
Clean handover
Access, documentation, and a live walkthrough for the people who will maintain the work. Nothing in the handover is engineered to require us.
Working principles
Four rules we keep to on every engagement, written down because they are easy to drift away from.
Column 01
Say what is out of scope
Every proposal carries an explicit exclusion list. Boundaries get clarified before the project starts, not in a change-order conversation three weeks in.
Column 02
Measure the thing you claimed to improve
If the project was about lead volume, reporting is about lead volume. Not page speed, not aesthetics — the measure the engagement was sold on, tracked from launch.
Column 03
Hand over cleanly
Access, documentation, and a walkthrough for the people who will maintain the work. No dependency engineered into the handover, and no retainer held hostage.
Column 04
Flag problems early
We would rather have an uncomfortable conversation in week three than a surprised one at launch. When something is not working, you hear it from us before the review meeting.
Tooling
The tools we use and why
We are platform-agnostic in principle and opinionated in practice. A platform earns its place when the client's team can actually run it after handover.
Webflow
Used when a client needs design control and a custom CMS workflow their team can edit directly, without a developer in the loop for every copy change.
Wix
Recommended when speed to launch and simplicity matter more than bespoke structure. That happens more often than most agencies like to admit, and pretending otherwise usually costs the client money.
WordPress with AIOSEO
On WordPress builds we configure AIOSEO for sitemaps, schema, and on-page structure, so the site's technical foundation is readable to search engines from day one.
Jotform
For intake, Jotform handles multi-step forms and conditional routing when a single form cannot cover the qualification logic your team actually needs.
Public review platforms
Google Business Profile, Trustpilot, and the Better Business Bureau influence whether someone trusts a business before they reach its site. Ignoring them because they are off-site does not make them less real.
The team's shelf, not a slide deck of platform logos. The tools get chosen to match the work.
If the argument for a platform cannot survive a year of your marketing lead editing pages without help, it is the wrong argument.
Limits
What we don't do
The shortest path to a bad engagement is pretending a firm does everything. These are the boundaries we hold to.
Out of scope
We don't run paid media campaigns
We advise on the landing pages and the measurement, then work alongside whoever manages your ad spend. If you want one firm to run the media and build the receiving pages, we are not the right call.
Out of scope
We don't provide legal, financial, or tax advice
Nothing on this site should be read that way. Where a project touches regulated ground, we work alongside your counsel rather than standing in for it.
Out of scope
We don't take on projects where the goal cannot be stated in a sentence
If it cannot be written down, it cannot be measured, and unmeasured consulting is just billing. When the goal is still fuzzy, we start with a scoping engagement and revisit the decision at the end of it.
Questions
Things clients ask before signing
Straight answers to the questions that usually decide whether we are the right fit. If yours is not here, ask it on the contact page.
Do we need to be in the DC area to work with you?
No. Most engagements run remotely with U.S. clients. Being nearby helps for kickoffs, workshops, and final walkthroughs, and we travel around the DC metro area for those, but day-to-day work happens over calls and a shared written plan.
Who actually does the work?
The delivery lead you meet at kickoff stays through handover. Typical engagements use two to four people, most of them the same names you met at the start. When a build needs extra hands, they join the same person's team rather than a parallel charter.
Will you tell me if a rebuild is not the right answer?
Yes, and it happens more than you would expect. Before proposing a rebuild we look at what your traffic and conversion numbers say. If the site is not the bottleneck, we say so and put the recommendation in writing.
What does a proposal from Penthoria Digital contain?
A written scope of work, an explicit exclusion list, the measure we will report against, and the names of the people who will deliver it. If any of that is missing, ask for it — the proposal is a document you should be able to forward to your team without editing it first.
Where does the work go after handover?
To your team, with access, documentation, and a live walkthrough for the people who will maintain the work. We do not engineer a dependency into the handover. If you prefer ongoing support after launch, we scope that separately and you are free to say no.
The honest way to judge a firm this size is a conversation, not a page. If you have a project in mind — or a project you are not sure should exist — book a consultation and we will tell you early whether we are the right fit.
Reach the firm
1201 Market Street, Suite 1500, Philadelphia, PA 19107
Monday to Friday, 9:00 AM – 6:00 PM Eastern Time
Ready when you are