Sylvia Ekabua designs CRM systems and workflow automations for businesses, connecting tools and improving processes such as lead follow-up, onboarding, and support routing.
Sylvia Ekabua is most useful for fixing CRM and workflow automations, especially lead follow-up and support routing.
Best for
A B2B marketing agency wants to fix lead follow-up automation with instant response and routing.
Not for
This is not for sponsored product promotion or broad reach campaigns with no implementation.
Key takeaways
A lead-response audit found 40 leads in 30 days, 21 never contacted.
They used JavaScript when standard CRM connectors could not handle support-ticket data.
After an API limitation, they rerouted communication through Twilio rather than forcing original plan.
Check first: Confirm terms, deliverables, approval process, and audience analytics before a paid brand partnership.
Main ideas
Your follow-up problem is bigger than your lead problem · Automation should give people time back, not just add more tools · Read the documentation before treating a platform limit as a bug
Sylvia Ekabua is a CRM and workflow automation specialist whose LinkedIn posts show how they connect tools and repair business processes, from lead follow-up and support routing to onboarding and reporting. Their posts pair practical troubleshooting with the business problem behind the technology: preventing inquiries from going unanswered and giving teams time back.
Ekabua makes automation concrete by showing the operational stakes and the messy details of implementation.
In one post, they audit a firm that contacted 19 of 40 leads and calculate the potential cost of unanswered inquiries; in another, they describe using JavaScript when standard CRM connectors could not handle support-ticket data.
Their troubleshooting shows restraint: after discovering an API limitation in a Boulevard–GoHighLevel integration, they rerouted the communication through Twilio rather than forcing the original plan.
Alongside technical posts about Make Data Stores, they emphasize that the goal is not more automation for its own sake, but faster follow-up, less manual work, and a more manageable inbox.
Their work shows how workflow design choices connect to those outcomes—and where a tool's limits may change the solution.
Sylvia Ekabua argues that automation should be judged by the business problem it removes, not by how many tools it connects.
Read more
Recurring priorities include faster lead follow-up, cleaner data moving between systems, and workflows that stay understandable as they grow. They treat platform limits and messy source data as normal parts of the work: read the documentation, reroute or parse when needed, and accept that “no-code” builds sometimes require code.
Your follow-up problem is bigger than your lead problem
Ekabua argues that businesses often buy more leads when the real problem is slow or missing follow-up.
Read more
The fix is instant acknowledgment and internal routing, not more ad spend.
An audit of a safety consulting firm found 40 leads in 30 days: 19 contacted and 21 never reached—about 52% lost to silence.
Ekabua estimated that 21 lost leads × 18% average conversion ≈ 3.8 deals × $8,000 ≈ $30,400 per month gone.
The pattern: a lead fills out a form at 6 PM, sits in a spreadsheet overnight, and gets a reply 14 hours later.
The proposed fix is an instant SMS acknowledging the inquiry and giving a call time, plus a Slack notification with full lead details.
It runs at 2 AM and on weekends for about $29/month.
Automation should give people time back, not just add more tools
Ekabua frames automation as a way to recover time and reduce manual work.
Read more
Tools are the route, not the goal.
One post describes a week spent in API docs and automation logic, then makes clear the goal was never more automation: it was giving an agency owner their evenings back instead of pulling reports until 9 PM, and making a support inbox feel manageable. In a service post, Ekabua calls the work building a “digital nervous system” with custom automations, KPI dashboards, and integrations across GoHighLevel, Make, Monday, Airtable, and Zapier.
A service post markets the tool stack; a later reflective post says the stack is never the point. The priority is the outcome, with tools as replaceable parts.
No-code work still needs logic, and sometimes code
Ekabua argues that the deeper an automation goes, the less the “no-code” label describes the work.
Read more
Logic matters more than the tools, and cleaning messy data may require a script.
A support-ticket automation was supposed to trigger as soon as a customer submitted a request, but the data arrived in a tangle that standard CRM connectors could not interpret.
Filters and conditions inside Zapier kept failing, so Ekabua added a Code by Zapier step to parse and format the data before it reached the CRM.
The takeaway: “no-code” labels only go so far.
Ekabua describes starting from the assumption “I am not a developer” and moving to writing JavaScript when the problem demanded it.
This shows what happens when a no-code tool meets a data problem that filters and conditions cannot solve—and why automation builders still end up writing code.
Read more
Sylvia Ekabua describes a client support-ticket automation designed to trigger as soon as a customer submitted a request.
The data arrived in a tangle that standard CRM connectors could not interpret, and repeated filters and conditions failed.
The fix was a Code by Zapier step to parse and format the data before it reached the CRM.
They draw a lesson from the experience: the deeper an automation goes, the less the “no-code” label can hide the need for logic.
For brands planning a campaign
For a lead follow-up project, this shows Ekabua can use a Code by Zapier step when a form or portal sends messy data. A campaign brief could include a small parsing script in the routing build rather than assume every connector will work out of the box.
This shows why fast lead response matters and offers a simple audit method a business can run before buying more ads.
Read more
Ekabua audits a safety consulting firm that received 40 leads in 30 days and contacted 19.
The other 21 never got a reply.
They calculate that 21 lost leads at an 18% average conversion rate equals about 3.8 deals, and 3.8 deals at $8,000 each equals $30,400 per month in missed revenue.
A lead arrives at 6 PM, sits in a spreadsheet overnight, and gets a reply 14 hours later.
The proposed fix: an instant SMS plus a Slack notification with lead details, even at 2 AM or on weekends, for about $29 per month.
For brands planning a campaign
This fits a campaign about lead follow-up automation. It offers an angle built around response time, routing, and a measurable before-and-after: the same traffic and ad spend, with more revenue recovered from existing inquiries.
This shows how Sylvia Ekabua handles an integration that will not behave as expected and offers a practical troubleshooting habit.
Read more
While debugging a Boulevard and GoHighLevel integration, Ekabua spent an hour treating an API limitation as a bug.
The real issue was that Boulevard does not route certain data out through its API in the expected way.
Once they understood that, they moved the communication piece through Twilio, which proved cleaner than the original plan.
The takeaway is blunt: read the documentation before touching the tool.
Arguing with a system that is working as designed is expensive.
For brands planning a campaign
For a CRM and workflow integration plan, this shows how Ekabua handles platform limits: check the documentation, accept the wall, and reroute through another tool when that produces a cleaner result. A campaign focused on CRM and workflow integration can ask for a named fallback path when the primary API route is restricted.
This shows what Sylvia Ekabua builds, which tools they use, and the business problems they address.
Read more
Ekabua describes professionals stuck in manual chaos: onboarding, approvals, and spreadsheet updates.
The alternative is a dashboard that shows project status without clicking a button.
They call the work building a “Digital Nervous System” and list custom workflows, KPI dashboards, and integrations with GoHighLevel, Make, Monday, Airtable, and Zapier.
The post ends with an explicit offer to help two more businesses automate their chaos that month.
For brands planning a campaign
This is the clearest single post for matching a brief against Ekabua’s stated tool stack and service offering. For an agency lead follow-up brief, it shows a direct fit with GoHighLevel, Make, and Zapier, and sets expectations for a scoped engagement rather than a broad retainer.
This answers a specific design question: how to keep a workflow from becoming a pile of routers and hard-coded values.
Read more
Ekabua explains that Make Data Stores changed how they design workflows.
Instead of stacking routers or hard-coding everything, data stores help reduce duplicates, keep workflows organized, and cut unnecessary processing, which can save credits.
The post explains how they use them and asks other builders how they handle “memory” in automations.
For brands planning a campaign
For a lead follow-up build, this points to a concrete architectural choice: use a data store to check whether a lead has already been contacted, prevent duplicate messages, and route follow-up steps without piling on routers. A campaign could present this as the memory layer behind instant response.
This shows why the automation work matters beyond the tools and gives newcomers a plain-language explanation of the purpose behind the technical posts.
Read more
Ekabua writes about spending the week in API docs and workflow logic, staring at a field that should be simple.
The point is that the work is not about adding automation for its own sake.
It is about giving an agency owner an evening back instead of having them pull reports until 9 PM, and making a support inbox feel manageable.
The tools deliver the outcome; they are not the point.
For brands planning a campaign
For a campaign brief, this supports an outcome-first framing: measure the build by hours returned, response speed, and whether the support inbox becomes manageable—not by the number of automations added.
Ekabua's most concrete worked example audits a safety consulting firm: 40 leads arrived in 30 days, 19 were contacted and 21 were never reached—roughly 52 percent of inquiries lost to silence.
Read more
The post converts that into money (21 lost leads × 18% average conversion ≈ 3.8 deals × $8,000 ≈ $30,400 a month) and traces the pattern to slow response: a form filled at 6 PM sitting in a spreadsheet overnight and getting a reply 14 hours later.
The proposed fix is a low-cost automation that sends an instant SMS acknowledging the inquiry with a proposed call time, plus a Slack notification to the team carrying the full lead details, running at any hour rather than during office hours only.
Ekabua cites industry data that leads contacted within five minutes are nine times more likely to convert than those contacted after 30 minutes, and says most service businesses average four to six hours.
Audit steps given to readers: open the CRM, filter to leads from the last seven days, and count how many have not been contacted.
The conversion rate, deal value and revenue figures come from a single audited firm, and the five-minute industry statistic is quoted without a named source. Treat the numbers as an illustration of the argument, not a benchmark to reuse for another client.
For brands planning a campaign
This is the clearest match for a brief about fixing lead follow-up. The post supplies an audit method, a financial framing and a specific minimum build (instant acknowledgment plus internal routing), so a campaign can move straight to scoping response times, routing rules and the CRM fields involved.
Working inside platform limits: reading documentation before building
A post about debugging a Boulevard/GoHighLevel integration describes an hour spent treating a limitation as a bug before discovering that Boulevard simply does not let certain data route out through its API in the expected way.
Read more
Once the limit was accepted, the communication piece was routed through Twilio instead, which Ekabua describes as cleaner than the original plan. The stated lesson is to read documentation fully before touching a tool, not to scan it.
Read the platform documentation end to end before configuring, then redesign the data path where a limitation is structural rather than a defect.
For brands planning a campaign
Useful when a brief involves connecting a CRM to a booking, scheduling or field-service platform. Budget for discovery time on each platform's API limits, and expect some requirements to be met by routing around one tool rather than forcing it.
Writing code inside no-code tools to clean messy data
Ekabua describes a support-ticket automation where form submissions arrived in a tangled format the standard CRM connectors could not read.
Read more
Filters and conditions inside Zapier kept failing, so a Code by Zapier step was written to parse and format the data before it reached the CRM. The post argues that the deeper an automation goes, the less the 'no-code' label covers the work, and that logic matters more than which tools are used.
A Code by Zapier step placed before the CRM connector to parse and reformat one messy field, tested against live output before routing onward.
For brands planning a campaign
Relevant to briefs where intake data from portals, forms or legacy systems does not map cleanly onto CRM fields. It shows willingness to write JavaScript inside an automation platform rather than abandoning the requirement, and sets a realistic expectation that data shaping is part of the build.
Automation memory and deduplication with Make Data Stores
A post on using Make Data Stores describes moving away from stacked routers and hard-coded values.
Read more
Ekabua lists the benefits as reducing duplicates, keeping workflows organized and cutting unnecessary processing, noting that Data Stores can also save credits. The post is framed as an open question to readers about how they currently handle memory in their automations.
For brands planning a campaign
Valuable for campaigns involving recurring records, repeat submissions or the cost of running large automation stacks, where deduplication and processing efficiency matter as much as the automation logic. It also indicates a habit of testing newer platform features in live client work.
In a service-introduction post, Ekabua describes the work as building a 'digital nervous system' for a business: custom workflows, KPI dashboards and integrations across GoHighLevel, Make, Monday, Airtable and Zapier.
Read more
The problems named are manual onboarding, chasing approvals and updating spreadsheets, and the promise is a dashboard showing project status without manual clicking. The same post states availability for two more businesses that month.
For brands planning a campaign
This is the fastest check of whether a brief's existing tools overlap with demonstrated platforms. Because the post is a pitch rather than a project write-up, confirm specific platform depth against the other items before committing a brief with unusual stack requirements.
A short reflective post says a large part of the week is spent in API documentation and automation logic, and reminds readers that the point was never more automation.
Read more
The outcomes named are an agency owner getting an evening back instead of pulling reports until 9 PM, and a support inbox that does not feel like drowning. Tools are described as the route to those outcomes rather than the goal.
For brands planning a campaign
Useful for campaign positioning: the value story is recovered time and reduced manual load, not the number of connected apps. A campaign angle built around hours returned or processes removed will match how this creator frames the work.
Sylvia Ekabua's posts show the platforms they build on rather than brand partnerships.
Read more
GoHighLevel, Zapier, Make, Boulevard, Twilio, and Slack appear as tools inside client automation work they describe in detail: a support-ticket automation, a CRM integration, a lead follow-up fix, and a workflow redesign.
They also describe auditing a safety consulting firm losing inbound leads, but do not name the firm; ask for a reference if that case study matters.
Monday and Airtable appear only in a list of tools Ekabua integrates, with no example of their use.
GoHighLevel
Mention
Ekabua writes about building and debugging GoHighLevel integrations.
Read more
In one post they describe spending an hour treating a data-routing limit as a bug before learning that Boulevard's API would not emit certain data. They later list GoHighLevel among the platforms they use to build custom workflows and KPI dashboards.
Ekabua describes a client support-ticket automation in Zapier where standard CRM connectors could not read the incoming data, so they wrote a Code by Zapier script to parse and format the fields before they reached the CRM.
Read more
They also name Zapier among the tools they integrate for clients.
Ekabua describes redesigning workflows around Make Data Stores, saying they let them reduce duplicates, keep workflows organized, and cut unnecessary processing and credit use.
In the same integration story, Ekabua rerouted the affected communication through Twilio after hitting Boulevard's API limit, calling the result cleaner than their original plan.
Ekabua's proposed fix for slow lead follow-up pairs an instant SMS auto-response with a Slack notification carrying full lead details to the client's team, so inquiries that arrive at night or on weekends still get routed.
Sylvia Ekabua publishes on LinkedIn, and those posts are the place to start.
Read more
Begin with the lead-response audit, which makes the argument they return to most often: slow or missing follow-up loses revenue that more ad spend cannot recover.
It also offers a practical check: open the CRM, filter to leads from the last seven days, and count those nobody has contacted.
Next, read the integration and debugging posts, which show how they work when a platform does not behave as expected, then the posts about memory written for other automation builders.
Two looser posts sit alongside the technical ones: one lists the tool stack they build with, and the other explains why the tools were never the point.
Readers looking for more on CRM and automation can compare Ekabua with the creators listed below; each comparison explains what they share and where their work differs.
Both writers argue that tool complaints often disguise process or data problems, and prescribe mapping how work actually flows before automating anything.
Read more
Jared puts it directly: if marketing turns on the tap and the team starts seeing duplicate emails, missed leads and broken reports, the fault is the human patchwork underneath, not Zapier. Both also describe running a structured diagnostic: Jared maps lead to deal to fulfillment to payment, while Ekabua checks which leads went unanswered and reroutes around an uncooperative API.
Jared's posts focus on diagnostics and the questions a team should consider, packaging the work as a named revenue system integrity exercise. Ekabua's posts go deeper into the build, showing API limits, a Twilio reroute and a parsing script written inside Zapier.
Both judge integration work by its effects on customers and staff, not by internal tidiness.
Read more
Levi traces disconnected sales, support, project and billing systems to repeated questions, lost context and slow responses, and asks whether the CRM is genuinely ready before a company buys AI voice automation. Ekabua makes the same forward-looking point from the build side: logic and clean data matter more than adding another app layer.
Levi approaches readiness as a checklist of prerequisites—clean data, agreed definitions and stages that match the real sales process—and frames the payoff as a better customer experience across touchpoints. Ekabua shows those same standards applied mid-build, using documentation reading, data parsing and rerouting as examples.
Both treat automation as something that should become a maintainable system, not a pile of one-off connections, and identify scattered logic, undocumented rules and fragile connections as the real liabilities.
Read more
Belcher describes prompts hidden in black-box tools and business rules buried in Slack threads; Ekabua describes replacing stacked routers and hard-coded values with data stores that reduce duplicates and unnecessary processing.
Belcher writes as part of a team that offers B2B revenue teams a versioned, owned code repository and embedded go-to-market capacity.
Ekabua writes as an individual specialist who works mainly in visual platforms such as Make, Zapier and GoHighLevel, using code selectively when a data problem demands it.
Their focus is service businesses losing leads rather than enterprise revenue operations.
Sylvia Ekabua’s posts make the subject matter relevant to a B2B campaign about CRM and lead-follow-up automation aimed at agencies: they discuss missed inquiries, workflow design, integrations, and practical debugging.
Read more
Before deciding on a placement, ask for recent audience analytics and, if the campaign depends on reaching agency owners or other job roles, documented audience survey results or another source identifying those roles.
Sylvia Ekabua's posts focus on client service work, not a sponsorship program, media kit, rate card, or published brand-partnership offering.
Read more
They describe designing and repairing CRM and workflow automations for businesses through individual projects rather than commercial packages.
Examples include connecting GoHighLevel, Make, Monday, Airtable, Zapier, Twilio, and OpenAI; building dashboards; and fixing lead follow-up, onboarding, and support routing.
The posts do not state terms, deliverables, rates, exclusivity, timelines, or approval processes.
Their offer-like statements are service capacity and a free lead-response audit, both aimed at prospective clients rather than brands seeking promotion.
No partnership format or official inquiry route is published.
Ask directly whether they undertake brand partnerships and, if so, to establish scope and terms.
Strong fit for an implementation-focused engagement. This is the brief the reviewed work speaks to most directly.
Read more
Brief
A B2B marketing agency wants to fix lead follow-up automation with instant response and routing.
Reasons
The lead-response audit is the clearest match: it describes 40 leads in 30 days, 21 never contacted, and a proposed fix using instant SMS acknowledgment plus a Slack notification with full lead details, running outside office hours.
The work shows a willingness to use a Code by Zapier step to parse and reformat messy form or portal data before it reaches a CRM—useful when intake data does not map cleanly onto standard connectors.
The work shows a practical response to platform limits: after finding that a booking platform would not route certain data as expected, Sylvia Ekabua moved the communication piece through Twilio instead of forcing the original path.
The work adds a useful design layer for follow-up builds: Make Data Stores used for deduplication, contact history, and reducing unnecessary processing.
The posts name a tool set relevant to an agency brief, including GoHighLevel, Make, Monday, Airtable, Zapier, and KPI dashboards.
Watchouts
The posts describe client service work, not a sponsorship or influencer program. Establish terms, deliverables, and approval processes separately for a paid brand partnership.
The revenue and conversion figures come from one self-reported audit. Treat them as an illustration of the argument, not as benchmarks for another client.
Ask for audience-composition and reach data before assessing a brief that depends on either.
When to choose a specialist
Poor fit as described.
Read more
Brief
A B2B SaaS company wants a sponsored LinkedIn thought-leadership series to promote a new AI sales assistant to a broad executive audience, judged on reach and brand awareness, with no implementation component.
Reasons
The posts show service work and teaching about CRM and automation projects, not sponsored product promotion or a track record of brand-funded thought-leadership series.
The posts include no media kit, rate card, sponsorship formats, or partnership inquiry route. The only offer-like statements are service capacity and a free lead-response audit aimed at prospective clients.
Without audience-composition or reach data, a brief judged primarily on broad executive reach cannot be assessed.
The demonstrated strength is practical, tool-and-process-specific work: lead routing, API constraints, data cleanup, and process memory. A broad brand-awareness series would not use that strength.
The posts contain no independently verified client results, weakening a pitch built on performance claims.
Reconsider if
If the SaaS company reframed the campaign as a technical implementation webinar, a paid audit, or a product-based automation build, the fit would be different. Ask for examples of that work before proceeding.
A worked campaign example
Brief
A B2B marketing agency wants to fix lead follow-up automation with instant response and routing.
Campaign angle
The five-minute lead rescue. Use Sylvia Ekabua to audit the agency's own lead response, then build and test the first version of an instant-response and routing automation. Frame the campaign around recovered inquiries rather than more ad spend.
Measurement
Median first response time before and after the build.
Percentage of leads from the last seven days that received a response.
Recovered deals calculated with the client's own conversion rate and deal value.
Duplicate follow-up messages or records prevented by the data-store check.
Plan
Audit: open the CRM, filter to leads from the last seven days, and count how many have not been contacted. Build a before snapshot using the client's own conversion rate and average deal value, not the figures from the post.
Design: add an instant SMS acknowledgment with a proposed call time, plus a Slack or Teams notification to the team carrying the full lead details. Include after-hours and weekend routing. Use Make Data Stores as the memory layer to check whether a lead has already been contacted and prevent duplicate messages.
Build around limits: inspect the CRM, booking, and support-platform APIs before configuring. If a platform blocks outbound routing, move the communication piece through Twilio. If portal or form data arrives in a format standard connectors cannot read, use a Code by Zapier step to parse one messy field before it reaches the CRM.
Dashboard: show median first response time, percentage of leads contacted within the target window, and leads waiting for a reply.
Test: submit an after-hours test lead and confirm the SMS sends, the Slack notification arrives with full details, the CRM record is created or updated correctly, and no duplicate follow-up is triggered.
Why this works
It uses Ekabua's demonstrated methods; ask for documentation before relying on self-reported commercial results. The posts show a service and implementation fit, not a documented sponsorship offer.
Choose Jared W. when the follow-up failure is a symptom of a revenue system nobody trusts.
Read more
The posts frame the identical problem — broken response, duplicated records, missed leads — as a system-integrity issue first: before wiring any automation, map the path from lead to deal to fulfillment to payment, mark where humans improvise, where data duplicates, and where rules never existed, then decide what is safe to automate.
If the agency has already rebuilt its CRM two or three times and still cannot say where revenue leaks, that diagnosis-first sequence addresses the actual cause, while a straight instant-response build would paper over it.
The posts also supply a sharp test for a campaign aimed at diagnosing the same problem: if every automation were switched off tomorrow, would the team still trust its numbers?
The posts stay at the diagnostic and framing level.
They describe what to map and which questions to ask, but they do not show the specific build mechanics a campaign aimed at delivering a running follow-up workflow this month needs — no instant SMS acknowledgment, no after-hours routing, no working example of parsing messy intake data before it reaches a CRM.
An agency that needs a running follow-up workflow this month would still need someone to implement it.
Choose Irit Levi when the follow-up problem is really a data-quality and cross-system integration problem, or when the agency is weighing an AI voice or answering tool and needs a readiness check before spending.
Read more
The posts make the case directly: a company can spend heavily on AI voice automation and only then discover duplicate records, incomplete data, undefined pipeline stages, and manual processes that should have been automated years ago; the right question is not whether a tool works with the CRM but whether the CRM is ready for it.
The same framing extends the blast radius outward — sales CRM, support ticketing, project management, and billing that do not talk to each other produce customers repeating themselves, lost context in handoffs, and slow responses.
That is useful when the agency's instant-response build depends on clean, agreed definitions of a qualified lead.
The posts are cautionary and readiness-oriented rather than instructional.
They list the conditions that must be true and the failure patterns to look for, but they do not walk through configuring an instant-response or routing workflow, so an agency wanting the build itself gets less concrete implementation guidance than from the subject of this page.
Before buying, ask for a named-tool example of a tested build.
Choose Benton Belcher when the agency wants the whole go-to-market execution layer rebuilt as owned, versioned code rather than one fixed workflow.
Read more
The posts describe scattered logic as a liability — prompts hidden in black-box automation tools, one-off scripts on a single laptop, business rules buried in Slack threads, field mappings lost in the CRM — and propose packaging routing logic, intent signals, and enrichment rules into a single documented repository that the client owns, with the strategy and media plan kept on the client side. That is a better match than a single workflow build when follow-up breaks because the same rules live in several places and nobody can explain them, or when the agency wants embedded capacity across marketing, sales, revenue operations, and data rather than a one-off fix.
The engagement is broader and heavier than the need for a lead-follow-up campaign implies.
The posts describe a full execution architecture and embedded services, not a quick instant-response and routing build, so an agency wanting a single workflow repaired may end up buying a larger redesign.
The posts do not show the mechanics an instant-response and routing campaign needs — no instant acknowledgment, no routing configuration, no after-hours handling.
Ask for examples of those mechanics, along with client results, pricing, and timeline.
Sylvia Ekabua has six complete LinkedIn posts about CRM and workflow automation.
The posts cover a lead-response audit, a Boulevard and GoHighLevel integration fix, a Code by Zapier support-ticket build, a Make Data Stores workflow, a service and tool-stack overview, and a reflection on what automation is for.
Topics, ideas, working methods, tool mentions, and fit decisions on this page come from those posts.
Similar-creator comparisons refer to posts from three other automation writers, drawing on their own stated arguments rather than treating them as hiring scenarios.
The dates of Ekabua's posts are not stated, so the page does not claim a posting timeline, and Ekabua's posts here do not identify sources beyond LinkedIn.
Two gaps remain: Ekabua's posts do not establish whether they have signature books, shows, businesses, or earlier career work, and the posts here do not provide a media kit, rate card, sponsorship formats, audience-composition figures, or independently verified client results.
Commercial fit notes therefore rest on demonstrated service work and working methods, not on a documented partnership offer.
