What is built, and what is run.
Two headings, not six, and they are stages of the pipeline. Two lines produce a thing in design and build. Four hold a responsibility in operate, and that group is the business. No line has a colour of its own; the stage does. There are no tiers, no packages and no price table for engagements; the scope, the cadence, the term and the exit are published instead.
Built, in the design and build stages
The identity, and the document set an institution is handed. Built once in the design stage, then kept current as part of operating.
The public surface and what sits behind it: the site a vendor-risk reader checks, the portals a function uses.
The front of the pipeline. Built in the design stage, beside the architecture.
Run, in the operate stage
The operational systems the function runs on, monitored and kept up; a stated allowance of change work per month; incident response within a stated window; code and credentials held in your name.
The reporting layer kept running and read: dashboards maintained, a monthly analysis in plain words, models retrained on a stated schedule.
What the function publishes and sends, produced in your voice against a calendar texxen keeps, with the measurement of each piece.
Channels run and spend managed inside a budget you set, with weekly reporting and a monthly recommendation on where the next peso goes. Never a percentage of spend.
Every operated line carries a weekly note and a monthly review.
Three ways an engagement is paid for
The build fee
Scoped from the diagnostic and set at the proposal. Not published. Covers the design and build stages against a signed scope.
The operated retainer
A fixed monthly fee scoped to what is covered, never to headcount or spend. For institutions the term is annual or longer, with continuity and exit obligations. [institutional terms, question 4]
A product deployment
A starting price per deployment into your own cloud account, published on the product’s own site. From [PHP amount]. texxen operates it there on the retainer, which is the standard shape; self-run where your policy requires it, priced separately.
How an engagement starts
With the diagnostic: two to three weeks, a fixed fee, and a document that pairs every defect with its fix and names the layers worth doing after the first. It can end there.
Ownership, on every engagement
- Code and credentials for what is built are held in your name.
- On a product, the instance runs in your own cloud account and is yours, with your data, your configuration and your extensions. texxen keeps the product core. [proposed, awaiting confirmation]
- Source code escrow where your risk function requires it.
- An exit that works: the record and the running systems leave with you. [exit obligations, question 4]