How we workInside the engagement

You always know exactly where things stand.

When you hire us, you don’t get left in the dark between status calls. Every engagement runs in a private client portal — one place for live milestones, line-item pricing, a written reason for every change, two-way email, and an audit log you keep. This is what working with RESILIENCE looks like from the inside.

See inside the portal Begin a conversation

The room where we work

Here is the room where we work. You’re handed the keys.

Every active engagement lives in a private portal — a single surface for milestones, line-item pricing, files, decisions, and two-way email. It’s the same RESILIENCE software running our own shop, not a third-party tool, presented the way a print magazine would present an artifact.

RESILIENCEClient portal

The live view of your project

Phase 1 of 3 in progress. You’ve paid 55% so far, and your next walkthrough is Thursday at 10am.

Where the money stands$25,000.00 total

Private client portal · the same software running our own shop

How the work happens

From the first email to handover.

Seven moments in a typical engagement — each paired with the actual portal surface that carries it. The layout, the typography, the cyan accent: what you see here is what you sign into.

01Before anything is signed
You send the brief. A senior engineer answers.
No funnel, no junior account manager, no chatbot. The person who reads your first note is the person who will write the proposal and ship the code. You get a straight answer on whether we're the right fit and what it would take — before any money changes hands.
02Day one
You're handed the keys and a discovery intake.
The moment we accept the engagement, you get a private portal URL, a password, and a short discovery intake. Five sections, around seventeen questions — it autosaves on every field, so you can step away and come back. When you submit, it locks read-only and we take it from there.
Discovery intakeAutosaved
About the work5/5
Constraints + risk3/3
Stakeholders2/2
Success4/4
Operating preferences3/3
Once you hit submit, we take it from here.
A short intake that saves as you go
03Money is legible
Every dollar is on one screen — paid, outstanding, remaining.
A single Trust Ribbon shows where the money stands at a glance. The Phase Board breaks the engagement into named line items, each with its own status and, when it's billed, a Stripe link to pay or download the receipt. No vague invoices, no end-of-project surprises.
Paid
$13,750
Outstanding
$5,000
Remaining
$6,250
Paid, outstanding, and remaining — at a glance
DepositBooked engagement$2,500Paid
Phase 1Foundation + auth$7,500In progress
Phase 2Portal + admin$7,500Pending
FinalHardening + launch$2,500Pending
Every part of the project, with what it costs and where it stands
04Every change has a reason
If the price moves, you get the why — in writing.
Any adjustment to the headline price, up or down, requires a written reason of at least twenty characters. That reason is logged immutably, shown in the portal next to the operator's name, and emailed to you with a before-and-after diff. The reason column is the trust.
Revision · 12 hours agoOperator
$20,000$25,000
Scope expanded to include an admin role and multi-tenant Stripe wiring; we'd rather price the new surface honestly than carry it as a hidden cost.
● Reason · 154 charsImmutable · client-visible
Every price change, with the reason in writing
05Live, not weekly
You watch the work happen, the moment it happens.
Pinned to the top of your project is a live timeline of milestones, files, decisions, questions, and replies. When something changes, the row fades in and settles — driven by the database itself, not a polling loop. No status calls to chase; you always know exactly where things stand.
Recent activityLive
ReplyNew client reply
Thursday at ten works on my end…
just now
MilestonePhase 1 — Foundation
Marked as in progress
2h
Filedesign-spec-v3.pdf
Uploaded by client · 1.4 MB
yesterday
DecisionHosting region locked to us-east-1
Logged on the project record
yesterday
Updates land the moment they happen — no refresh
06One thread, both ways
Reply to an email and it lands back in the portal.
When we write from the operator console, it reaches your inbox like any normal email. When you hit reply, your response threads straight back into the portal automatically. One conversation, in one place, however you choose to write it.
You2 days ago
Sending a quick check-in — the foundation phase is wrapped. Let me know when you're free for a fifteen-minute walk-through.
Clientclient@…
6 minutes ago
Thursday at ten works on my end. The portal makes it easy to keep up between calls — appreciated.
Reply by email and it lands right back here
07On your terms, through to handover
You choose how we reach you — then we hand it all over.
Email, web push, and estimate updates are each their own toggle, so you set the signal you want without going dark. And when the build is done, the portal stays the record: the intake, the phases, the reasons, and the audit log are yours to keep.
How we reach you
Email
Web Push
Estimate updates
You choose the channels that reach you

Selected work

Work we can describe.

Anonymized engagements, in the numbers that mattered to the business. No names, no jurisdiction tighter than region — the restraint is the credibility.

Software development2025

A regional wholesale distributor, US Midwest

A single operations platform that replaced nine spreadsheets and a brittle vendor portal — order to invoice, on one source of truth.

Systems of record consolidated: 9 → 1
Order-to-invoice cycle: 3 days → 40 min
Ongoing vendor-portal license cost: 0

The distributor ran on a decade of accreted tooling: order intake in one spreadsheet, inventory in another, pricing in a third, and a legacy vendor portal nobody could change without a support ticket and a wait. Every quarter-end was a reconciliation marathon, and a single fat-fingered cell could ship the wrong price to a wholesale account. The engagement was a custom operations platform — built from a blank repository — that unifies intake, inventory, pricing, and invoicing behind one typed data model the team owns outright.

Methodology

01
Model the operation, then the screens
We mapped the real order-to-cash flow with the people who run it before writing a line of UI, so the schema matched the business instead of the previous tool's limitations. Every record carries an audit trail from day one.
02
Migrate without a freeze
The nine spreadsheets and the vendor export were imported behind a reconciliation harness that flagged every mismatch for a human, so the cutover happened alongside live operations rather than over a risky weekend blackout.
03
Integrations, not lock-in
Accounting and shipping connect through typed, documented APIs the distributor controls — no proprietary portal, no per-seat tax, no waiting on a vendor's roadmap to add a field.
04
Handed over, not held hostage
The platform shipped with the repository, the data, and the documentation in the client's hands. The managed-care retainer is a choice, not a dependency.

One platform the business owns — built to outlast us.

Source notes redacted · Client identification withheld by agreement

Websites & apps2026

A professional-services firm, US Northeast

A rebuilt marketing site that loads in under a second — plus the managed-care retainer that keeps it fast, current, and never broken on a Friday.

Largest contentful paint: ~5s → <1s
Median turnaround on care requests: 48 hr
Unplanned downtime under care: 0

The firm's old site was a slow, plugin-laden build that took five seconds to paint, broke on every other content edit, and quietly leaked prospective clients on mobile. They did not want a redesign treadmill — they wanted a site that felt deliberate, converted the visitors they already had, and stayed handled. The engagement was a ground-up rebuild on a modern stack, followed by the affordable monthly managed-care retainer that owns uptime, updates, and edits so the firm never has to.

Methodology

01
Rebuild on a stack that stays fast
Server-rendered, no plugin sprawl, images and fonts optimized at build time — the kind of foundation that holds its performance instead of degrading with every addition.
02
Design for the decision, not the award
Every page points at one next step. We instrumented the funnel so copy and layout changes are judged on whether prospects actually move, not on taste.
03
Accessibility and SEO as build constraints
Keyboard-operable, contrast-checked, structured data and clean metadata shipped on day one — credibility signals that compound quietly in search.
04
Managed care, not a maintenance invoice
The retainer covers hosting, monitoring, dependency updates, and content edits with a committed turnaround — so a typo or a new service page is a quick note to a senior engineer, not a project.

Built once to hold, then quietly kept that way.

Source notes redacted · Client identification withheld by agreement

Agentic AI2026

A B2B services firm, US Southeast

An agent-in-the-loop operations desk that triages every inbound, drafts the first reply, and never acts without a human holding the last word.

Inbound triaged without human touch: 70%
Median first-response time: 4 hr → 18 min
Outbound actions human-approved: 100%

The firm's two-person operations team had become the bottleneck on its own growth: every inbound enquiry, scheduling request, and document hand-off ran through the same two inboxes, and the backlog grew faster than they could hire. They did not want a chatbot bolted to the website — they wanted the repetitive judgement work handled and the human judgement preserved. The engagement was a custom agent that plugs into the tools they already run — mailbox, calendar, and document store — triaging inbound, drafting context-aware replies, and preparing scheduling, with every outbound action staged for a one-click human approval.

Methodology

01
Tool boundaries written before prompts
We enumerated exactly which systems the agent may read and which actions it may take — and, more importantly, the ones it may never take unattended. The boundary is enforced in code, not asked for politely in a prompt.
02
Agent in the loop, not human out of it
Every outbound email, calendar invite, and document edit lands in an approval queue with the agent's reasoning attached. A person approves, edits, or rejects in one click. Nothing reaches a client without a human signing off.
03
Model selection against a cost and privacy posture
Routine triage runs on a smaller, cheaper model; only genuinely ambiguous cases escalate to a frontier model. Client data stays inside boundaries the firm controls, with no training on their correspondence.
04
Adversarial testing before production
We red-teamed the agent against prompt injection in inbound mail and malformed attachments before it touched a live inbox, so a hostile message can't talk it past its own guardrails.

The agent does the repetition. The team keeps the judgement.

Source notes redacted · Client identification withheld by agreement

Blockchain & smart contracts2025

A DeFi lending protocol, scope redacted

A full-stack smart-contract security audit — findings by severity, refusal lanes enforced, operator sign-off on every mitigation.

Critical finding (mitigated pre-mainnet): 1
Contracts in scope: 4
Operator sign-off on mitigations: 100%

The protocol was preparing a mainnet upgrade across four core contracts and needed an audit that read like engineering, not a marketing PDF. The engagement was a structured security review — static analysis, symbolic paths, and manual review — bound by refusal lanes that forbid automated mainnet execution, fund movement, or performance claims. Every finding is severity-banded; every recommendation waits for the client's security lead to accept, defer, or reject.

Methodology

01
Refusal lanes before tooling
Documented the no-list first: no mainnet deploy without signed release, no live fund movement, no yield or return language in the audit surface. The tooling respects the same boundaries the final report does.
02
Layered analysis surface
Static analysis for known vulnerability classes, symbolic execution on critical paths, manual review on access control and oracle wiring. Findings keyed to contract, line range, and reproducible test case.
03
Severity-banded reporting
Critical and High findings block the release record until acknowledged or mitigated. Medium and Informational ship with explicit deferral options — nothing silently dropped.
04
Operator owns every mitigation
Recommendations are drafted; the client's security lead decides. Every decision is logged immutably. The integrity metric is 100% operator sign-off, not finding count.

The audit surfaces risk. The operator decides what ships.

Source notes redacted · Client identification withheld by agreement

search-and-growth2026

A professional-services practice, US Southeast

An owned visibility stack — Search Console, answer-engine probes, a citation board, and a machine-readable site graph — with no rented pixel and no ranking claim.

Assistants probed each week: 3
Owned citation board: 1
Third-party pixels installed: 0

The practice needed to see whether search and answer engines could name it, without installing a third-party tracker or buying a mention it could not contract. The engagement was an owned visibility stack: daily query and impression sync, weekly probes across three assistants, a citation board for directory and entity hygiene, and an llms.txt plus schema graph the crawlers could actually read. Outcomes are delivery facts. Traffic and mention-rate figures were left off the record on purpose.

Methodology

01
Owned measurement first
Wired Search Console into a private store the operator can export. No GA4, no Meta pixel, no session replay. If a signal could not live in owned data, it was not a signal.
02
Probe the assistants a buyer uses
Weekly prompts against Claude, ChatGPT, and Gemini — named at rank, or not named. A miss became a content brief, not a screenshot in a deck.
03
Citation board, not a backlink package
NAP consistency, directory presence, and sameAs hygiene tracked as a queue the operator works. The lever no on-page rewrite can fake.
04
Machine-readable site graph
llms.txt, per-pillar FAQs, Service and FAQPage JSON-LD, offering and resource URLs. Schema restates the visible page. Nothing fabricated for a city without an office.

The stack makes naming possible. It does not contract a mention.

Source notes redacted · Client identification withheld by agreement

Why we work in the open

Transparency isn’t a feature. It’s the deal.

No status calls to chase
The activity feed updates live. You can check where things stand at midnight or on a Sunday without booking a meeting.
No surprise invoices
Paid, outstanding, and remaining sit on one ribbon. Every line item is named and priced before it's billed.
Every change in writing
A price can't move without a logged, client-visible reason. The record is immutable and emailed to you.
The audit log is yours
Intake, phases, decisions, and reasons stay in the portal after launch. The history is the contract.

The discipline

The portal is the receipt. The reason column is the trust. The audit log is the contract. You don’t have to take our word for any of it.

Open the room

Send us the brief. We’ll send back the keys.

Once we’ve accepted your engagement, you’ll receive a private portal URL, a password, and a discovery intake. The first row in your activity feed will be labeled “kickoff.”

Begin a conversation

You always know exactly where things stand.

Here is the room where we work. You’re handed the keys.

From the first email to handover.

You send the brief. A senior engineer answers.

You're handed the keys and a discovery intake.

Every dollar is on one screen — paid, outstanding, remaining.

If the price moves, you get the why — in writing.

You watch the work happen, the moment it happens.

Reply to an email and it lands back in the portal.

You choose how we reach you — then we hand it all over.

Work we can describe.

Transparency isn’t a feature. It’s the deal.

No status calls to chase

No surprise invoices

Every change in writing

The audit log is yours

Send us the brief. We’ll send back the keys.