The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
I help organizations win strategic contracts, secure funding, and communicate their capabilities through high-impact proposals, executive presentations, and consulting-grade documentation.
With 20 years of experience in management consulting and business development, I support organizations in preparing compliant, persuasive, and decision-ready submissions for solicitations, government tenders, donor-funded programs, consulting engagements, and corporate opportunities.
I have supported organizations preparing submissions and corporate materials for institutions such as USAID, World Bank, Asian Development Bank (ADB), UN agencies, DFID, and JICA, as well as clients across the public, financial, and corporate sectors.
Core Consulting Services
(A) Proposal Development & Bid Strategy
➙ Solicitation, IFB, RFP, RFQ, and tender proposal development
➙ Technical and financial proposal preparation
➙ Expression of Interest (EOI) and pre-qualification submissions
➙ Technical methodologies and project approaches
➙ Compliance matrices aligned with donor and procurement standards
➙ Bid structuring and evaluator-focused proposal strategy
(B) Executive Presentations & Pitch Decks
➙ Board, C-level and Customer facing presentations
➙ Consulting and advisory presentations
➙ Client pitch decks and bid presentations
➙ Investor and stakeholder briefings
➙ Technical solution and methodology presentations
➙ Corporate capability presentations
(C) Corporate Documentation & Capability Materials
➙ Capability statements and corporate profiles
➙ Organizational credentials and project references/Quals
➙ Proposal, EOI, and presentation templates
➙ Corporate reporting and deliverable templates
➙ Subcontractor and partnership documentation including NDA, MSA, and Teaming Agreements
Results Delivered
My work has helped organizations:
➙ Win multimillion-dollar government and donor contracts
➙ Secure funding from international development agencies
➙ Strengthen proposal compliance and evaluation scores
➙ Present complex technical solutions clearly to executive decision-makers
Business ConsultingTechnical WritingMicrosoft ExcelMicrosoft PowerPointMicrosoft WordBusiness Strategy
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
A one-way sync has a clear story: system A changes, system B follows. A two-way sync has a failure mode one-way syncs literally cannot have. The two directions can trigger each other.
Picture Zendesk tickets linked to Salesforce cases. An agent escalates, which writes a case in Salesforce. Engineering updates the case, which writes status back to the ticket. But that write to the ticket looks like any normal ticket change, so it can fire the escalation sync again, which updates the case, which syncs back to the ticket. Now both records are updating in a tight cycle. A runaway loop is worse than no integration at all.
Two controls stop it.
Actor exclusion: the integration writes through a dedicated user, and each side ignores changes made by that user. When the sync-back updates the ticket, the Zendesk trigger sees its own integration user and does nothing. You're telling each system not to react to itself.
Skip-unchanged guard: before propagating a change, compare the incoming value to what's already there. If nothing actually changed, stop. This catches the echoes that slip past actor exclusion, like a re-save that touches no real field.
The second hard problem is source of truth, and in a two-way sync it usually isn't one system. It's per field. Here, Zendesk owns the customer conversation and original context; Salesforce owns the engineering status and resolution. Neither owns the whole record. You decide ownership field by field, or the two directions quietly overwrite each other and call it a sync.
I wrote up the full design, including the status-mapping decisions between two systems that model status differently, as a spec and runbook below.
github.com
public-portfolio/03-salesforce-zendesk-case-escalation/case-escalation-spec.md at main · nodrel-dev/public-portfolio
Integration and systems documentation samples for SaaS ops teams — runbooks, specs, and architecture decision records, written from the codebase. - nodrel-dev/public-portfolio
Conversational Mechanics: Elevating Pitch Decks with Kinetic Contrast
Most integration documentation is written from interviews. Someone explains how the system is supposed to work, a writer transcribes it, and the doc captures the memory, not the system.
I do it the other way. I read the actual workflow exports, configs, and source, then document how the integration behaves in reality. When the doc and the system disagree, the system wins, because that's what I read.
The difference shows up later. Interview-based docs drift the moment a memory is wrong or a config changed after the conversation. Code-first docs match what's running, and every claim traces back to a specific artifact you can open and check 😍
Four full samples here, built on fictional but realistic scenarios: runbooks, a spec, a two-document package, and an architecture decision record, across n8n, Celigo, Salesforce, Zendesk, HubSpot, and NetSuite.
Trending
Claude
Claude has entered the design space. How are you using Claude Design?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
portfolioreview
The best portfolios tell a story, not just show a grid. Share yours for feedback.
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?