Keep business context with the work
Put brand knowledge, campaign decisions, customer insight, and operating rules where your team needs them.
Custom marketing technology Built for small business
Run your marketing.
Own the system.
A marketing stack built around your workflow.
I help small businesses connect their knowledge, tools, production, approvals, publishing, and reporting in one system their team can run.
Use the software you already rely on, add custom capabilities where they matter, and keep day-to-day marketing in your team’s hands.
Learn how the parts fit
15+ years across marketing, analytics, and systems
Based in the Philippines Experience with US and Australian teams
Your marketing should not have to fit someone else’s template.
Small businesses often outgrow a patchwork of generic tools, manual handoffs, and knowledge that lives in people’s heads.
Connect the marketing stack
Link production, approvals, publishing, tracking, and reporting instead of coordinating every step by hand.
Build the missing layer
Add focused interfaces, integrations, and AI-assisted capabilities when off-the-shelf software cannot support your workflow.
The result may combine tools you already use with custom software built for the parts that make your operation different. Your team gets the controls, documentation, and training to run it.
01 / Selected systems
Built from real constraints,
not hypothetical prompts.
What needed to change, which decisions mattered, and what was actually tested or delivered.
Context-aware marketing operations
Klaroha / BOS
One request.
A connected marketing workflow.
Klaroha explores how a small team can coordinate brand context, AI-assisted creative work, human approvals, asset storage, and publishing in one system.
Instead of rebuilding the brief at every production step, the workflow supplies the selected brand and campaign context where it is needed.
What this demonstrates
Separate a person’s request from the reusable knowledge and controls needed to carry it out reliably.
Tested behavior
The same simple instruction produced different creative outputs across three brand contexts. Completed publishing tests involved Meta, YouTube, and TikTok.
Scaled operations and long-term campaign intelligence remain unvalidated.
Shared brand + campaign context“Let’s post.”The operator supplies the intent.
The system supplies the context.
The system supplies the context.
- 01Concept & scriptModel generationHuman review
- 02Image & storyboardBrand-aware generationHuman review
- 03Video productionCreative generationFinal approval
- 04Store & publishSoftware-controlled distribution
MetaYouTubeTikTok
A simplified video path, not a live run. Output formats vary; publishing follows approval.
Production workflow & team handoff
AI-assisted legal content operation
A production workflow the team could run.
ControlGoogle Sheets
ProductionAI + automation
OutputWordPress
Research, drafting, imagery, formatting, issue monitoring, and publishing were connected behind a familiar Google Sheets interface.
SOPs and training enabled nontechnical staff to manage routine production without the builder coordinating every step.
What this demonstrates
Design the operating interface, documentation, and handoff alongside the automation—not after it.
Reported outcome
A fragmented production process became a repeatable operation with documented procedures and team ownership of routine work.
The full case distinguishes reported throughput from unverified content-quality, search, and business outcomes.
Data reuse & system-wide control
Real-time multi-asset trading architecture
Shared data. Coordinated decisions.
Per instrument1m source
Local resampling5m · 15m · 1h…
AuthorityPortfolio risk
Separate processing paths across assets and timeframes overwhelmed the available server. The redesign reused one-minute source data per instrument and derived larger timeframes locally in Python.
A portfolio-level controller governed allocation and trading permission above the individual strategies.
What this demonstrates
Find the architectural constraint before adding infrastructure, then place controls where the combined consequences appear.
Reported outcome
Multi-coin operation resumed on the available VPS after the data redesign.
An architecture case—not a claim of verified investment performance or measured compute savings.
02 / Build your marketing system
Your workflow first.
Then the technology.
I turn the way your business plans and runs marketing into a practical stack your own team can operate.
That may mean connecting existing tools, building a focused internal application, introducing a controlled AI workflow, or developing the system in manageable stages.
- 01
Map the marketing operation
Identify who does the work, what they need to know, which tools they use, where work slows down, and what a useful result looks like.
- 02
Build and connect the stack
Keep what already works. Add the interfaces, integrations, shared context, AI components, and controls the workflow actually needs.
- 03
Put it in your team’s hands
Test the complete workflow, document the operation, train its users, and define what your team runs versus what needs technical support.
03 / Learn to build in-house
See how the system works.
Build with better judgment.
Running marketing in-house starts with understanding what to connect, what context the system needs, and which decisions should remain human.
These free field notes unpack decisions from the projects—not just the tools used to implement them.
Available now: free field notes. Short conceptual notes, not full implementation tutorials. Step-by-step training, implementation assets, and deployable examples will be listed when ready.
Note 01 / AI-assisted development
Plan an AI-assisted build without losing direction
How I use multiple model perspectives, human synthesis, and a living project brief to keep implementation aligned with the intended operation.
Free · Field noteNote 02 / Workflow design
Separate creative generation from workflow control
Where models help—and why approval state, storage, routing, and publishing need explicit rules.
Free · Field noteNote 03 / Data architecture
Find duplicated work before adding infrastructure
How a scaling failure led to shared source data and locally derived analytical views.
Free · Field noteHave a workflow you want your team to learn?
Tell me what they need to accomplish, what they already know, and where implementation becomes difficult.
04 / The operating method
Design the complete workflow.
Not another disconnected tool.
Marketing experience shapes the build: begin with the commercial job, understand how the work moves, and choose technology only after the real constraint is clear.
Find the constraint
Define what the business needs to make possible and what is actually blocking it.
Connect the context
Bring the right knowledge, data, and operating rules into the workflow.
Generate where variation helps
Use AI for creative exploration, drafts, imagery, and other probabilistic work.
Control where certainty matters
Use software for state, approvals, storage, routing, and publishing—and people for consequential decisions.
Test the whole workflow
Evaluate whether the complete operation produces a useful result, then refine it.
A working component is not enough.
The whole workflow has to work.
05 / After the handoff
Your team runs the marketing.
Support keeps the stack moving.
Owning the operation does not mean your team must maintain every integration, model, or infrastructure component alone.
Ongoing support can be scoped around
- Maintenance and compatibility fixes
- Infrastructure administration
- Integration and model-provider changes
- Agreed upgrades as the operation evolves
Support responsibilities, response expectations, third-party costs, and new development are defined separately.
Discuss a build and its support needs06 / Marketing experience behind the build
Built by someone who understands
the work behind the stack.
I began in SEO, paid acquisition, websites, and analytics. The work expanded into customer journeys, reporting, team coordination, automation, and product development.
That experience helps me connect the technology to the marketing decision, handoff, or business result it needs to support.
Find opportunity before increasing spend
~1,000 → nearly 4,000Monthly bookings/ordersAt a service marketplace, analysis of historical acquisition data informed campaign restructuring and additional organic activity. Reported monthly volume reached nearly 4,000 within the first quarter after joining, without additional advertising spend.
Improve the economics of acquisition
$45–$60 → $9Reported cost-per-lead low, in USDAn established solar acquisition campaign reached a reported cost-per-lead low of $9 following restructuring and optimization—not a sustained average.
Make reporting useful and repeatable
Half a day → minutesRecurring reporting preparationCustom analytics reports and combined dashboards reduced recurring preparation from almost half a day to minutes. Following the registration-to-bidding journey also exposed an existing reporting error.
Historical, self-reported outcomes from previous engagements; not independently audited results or guarantees of future performance.
About Borj
I’m Borj.
I work across marketing operations, customer journeys, data flows, software implementation, and team handoff.
My focus is helping small businesses turn the way they market into systems their own people can use and improve.
AI expands what I can explore and build. Responsibility for the workflow, its decisions, and its results remains human.
07 / Next step
How should your marketing
work together?
Tell me how your team runs marketing today, which tools are involved, and where the workflow breaks down or slows down.
You do not need a finished technical specification.
jvcatingub@gmail.com Pampanga, Philippines · Remote collaboration