Skip to content
Bulwark BlackBulwark Black LLC
Latest
Quest Quanum Incident: Protect Patient Data While Keeping Orders MovingPulsar Token Bypass: Check Anonymous Fallback and Patch BrokersCisco Expressway Root RCE: Patch the Cluster and Check Service ReachabilityPulsar Manager Is Retired: Remove the Console and Recover Cluster CredentialsArista VCO Exploitation: Patch the Orchestrator, Review Every Portal RoleSafePay Warning: Prove Your Backups Can Survive an Administrator CompromiseTeamUpdraft Compromise: Check Every Connected WordPress Site for PersistenceRailway Secrets Incident: Rotate Credentials, Then Check What They Could ReachLiteLLM 1.107.0 Compromise: Rebuild the Environment, Recover the CredentialsGitLab Regex RCE: Patch the Server, Verify the Delivery ChaineMudhra CA Key Compromise: Check the Trust Stores Beyond Your BrowserPHP2Shell: Patch the Runtime Behind Your WebsitesTrusted Notifications, Untrusted Instructions: Close the Email Content GapBRONZE SANDCASTLE: Hunt the DLL Load Chain, Not the Trusted Executable
← Our software

Product case study · Built at Bulwark Black

Contractor Codex:
A connected client portal.

I built Contractor Codex to bring the administrative side of service work into a branded client portal. Quotes, agreements, billing, and project records belong to the same job; the application connects them while keeping each decision visible.

By Albert LaScola ·

Explore the workflowVisit Contractor Codex →

The problem

One job. Several handoffs.

A service job begins with a scope and a price, then moves through approval, delivery, invoicing, and payment. Changes along the way can affect the agreement and the amount owed. A portal needs to represent those transitions clearly for the business and its client.

Contractor Codex organizes those records around the client and the work. It supports project work and ongoing service commitments, with business branding carried into supported portal views and documents.

The product workflow

From an offer to a business record.

  1. Prepare the quote

    Choose the recipient, describe the work, and review itemized prices and billing terms. AI can help turn notes into a draft; quantities, exclusions, costs, and the finished quote still need review.

    Quote workflow →

  2. Record the agreement

    Send an agreement, quote, or change order through its signing path. An agreement’s body is frozen when sent; changes to signed scope use a separate change-order or replacement workflow.

    Agreement workflow →

  3. Bill for the work

    Choose the billing arrangement for the job, from upfront payment to deposits, completion drafts, or stages. Acceptance, invoice creation, and successful payment remain distinct states.

    Billing workflow →

  4. Review the records

    Bring contract value, billed and collected amounts, balances, costs, and hours into the project view. The usefulness of a report depends on the records entered and how they are classified.

    Project reporting →

Product decisions

Model the decisions behind the paperwork.

Make billing state explicit

A completion invoice can remain an unsent draft until someone reviews and finalizes it. Later progress or milestone payments follow their configured actions. Separating those states helps a business see what has been agreed, billed, and collected.

See how billing modes behave →

Distinguish service charges from provider costs

Hosting, domains, or API services may be paid directly by a client. The quote can disclose those recurring provider costs without adding them to the service business’s invoice. The application models the difference when the offer is prepared.

Explore provider-cost disclosures →

Review consequential AI actions

The admin assistant uses supported portal tools within the user’s permissions. Actions that require approval present the content, recipients, or amounts for confirmation. Preparing an invoice and approving its send are separate steps; some routine internal actions can apply directly.

Read the assistant’s action boundaries →

What this demonstrates

A working product, with defined boundaries.

The result is a connected business application with documented paths from quote preparation through billing and reporting. AI drafts need review and provider setup. Reports reflect the data entered, and contract templates need review for the intended work.

The linked product guides describe the supported workflows. Features and availability can change; consult the live product documentation for current details. Documentation reviewed October 22, 2026.

Have a business workflow that needs its own application?

I build client portals and web applications around the people, records, permissions, and decisions involved in the work. Start with the process you want to improve.

Discuss a custom web applicationWebsites and web app services

Another product build: SAMscout AI: a proposal workflow with human review →

Newsletter

The House-Of-L Brief.

Two short reads a day on markets, cyber threats, AI, and geopolitics. A "why it matters" line on every story.

Double opt-in. One-click unsubscribe on every issue. We never share your address.