{"id":5783,"date":"2026-04-16T19:31:02","date_gmt":"2026-04-16T14:01:02","guid":{"rendered":"https:\/\/cataligent.in\/blog\/uncategorized\/developing-business-model-vs-manual-reporting-what-teams-should-know\/"},"modified":"2026-06-10T04:37:44","modified_gmt":"2026-06-10T11:37:44","slug":"developing-business-model-vs-manual-reporting-what-teams-should-know","status":"publish","type":"post","link":"https:\/\/cataligent.in\/blog\/strategy-planning\/developing-business-model-vs-manual-reporting-what-teams-should-know\/","title":{"rendered":"Developing Business Model vs Manual Reporting: What Teams Should Know"},"content":{"rendered":"

Developing Business Model vs Manual Reporting: What Teams Should Know<\/h1>\n

Developing business model logic and producing manual reporting are often treated as connected tasks, but they solve different problems. A business model explains how value will be created, delivered, and measured. Manual reporting tries to describe what happened after work begins. When teams confuse the two, they may create impressive reports without building the execution structure needed to make the business model real.<\/p>\n

For enterprise leaders and consulting firms, the risk is practical. A team can design a new operating model, new revenue model, cost saving plan, or transformation roadmap, then manage execution through spreadsheets, email approvals, and slide decks. The report may look complete, but the work beneath it can remain fragmented.<\/p>\n

A business model needs execution logic<\/h2>\n

Developing a business model is not only about describing customers, revenue, costs, channels, partners, and capabilities. It also requires execution logic. Which initiatives will create the value? Which teams own them? What financial effects are expected? What approvals are required? What risks could block delivery? What evidence will confirm that the model is working?<\/p>\n

Without execution logic, the business model remains conceptual. A new subscription model may require pricing changes, sales process updates, billing system changes, customer support workflows, and finance reporting. A low cost market entry model may require channel partnerships, vendor changes, service design, inventory decisions, and marketing controls. Each part needs an owner, milestone plan, dependency view, and value tracking method.<\/p>\n

This is why operating model<\/a> clarity matters. Role clarity, responsibility mapping, governance forums, approval rights, and reporting cadence turn the business model from a presentation into coordinated work. Teams need to know not only what the model is, but how it will be executed.<\/p>\n

Manual reporting often hides the missing operating model<\/h2>\n

Manual reporting can be useful at the start because it is flexible. Teams can create a tracker quickly, adjust columns, collect updates, and build a slide for leadership. The issue appears when manual reporting becomes the operating system. At that point, the report becomes a substitute for governance rather than an output of governance.<\/p>\n

Common warning signs include different teams using different versions of the tracker, status colors based on personal judgment, approvals stored in email, finance validation handled after the report is written, and executive decisions recorded outside the reporting file. These weaknesses may not appear in the final slide, but they affect execution quality.<\/p>\n

For example, a business model may assume recurring savings from process automation. The manual report may show that the process redesign is complete. But unless the report also captures baseline cost, target savings, adoption evidence, actual cost movement, finance validation, and controller review, leadership cannot know whether the business model is delivering the promised value.<\/p>\n

What teams should model before they report<\/h2>\n

Before building a reporting pack, teams should model the execution structure. The structure should define the work hierarchy, ownership, financial logic, governance gates, and reporting cadence. This gives reports a reliable foundation.<\/p>\n

Useful modeling questions include: What is the smallest unit of work that can be owned and closed? Which initiatives roll up to which business model component? Which costs and benefits need to be tracked? Which approvals are required before execution? Which risks and dependencies should trigger escalation? Which reports are needed for workstream leads, the PMO, finance, and executives?<\/p>\n

Concrete examples include revenue uplift initiatives, cost avoidance actions, EBITDA improvement measures, one time implementation costs, recurring benefits, cash flow timing, supplier dependency, system readiness, customer adoption, process owner signoff, and controller backed closure. When these items are defined early, reports become easier to produce and more useful for decisions.<\/p>\n

Manual reports create control risk at scale<\/h2>\n

Manual reporting may work when a few people manage a small number of actions. It becomes risky when the business model depends on many teams, legal entities, geographies, or financial effects. As scale increases, manual reporting creates version risk, timing risk, ownership risk, and validation risk.<\/p>\n

Version risk appears when multiple files contain different status data. Timing risk appears when reports are already outdated by the time they reach leadership. Ownership risk appears when responsibilities are unclear or changes are not recorded. Validation risk appears when expected benefits are reported before finance confirms actual impact.<\/p>\n

These risks are not only administrative. They can affect the success of business transformation<\/a> work. A transformation office may need to control workstreams across cost, revenue, process, technology, and organization changes. If the reporting method is manual, the office spends too much time collecting information and too little time managing execution.<\/p>\n

Why the report should be a byproduct of governed execution<\/h2>\n

The strongest reporting model is not created at the end of the month. It is generated from the same system used to manage work every day. That means owners update measures, approvals are recorded, risks are escalated, financial values are maintained, and leadership reports draw from current controlled data.<\/p>\n

This changes the role of reporting. The report is no longer a reconstruction. It becomes a view into the execution system. Leaders can see whether initiatives are defined, decided, implemented, or closed. They can see which measures are on hold, which are cancelled, and which need decisions. They can also see whether value has moved from target to forecast to actual confirmation.<\/p>\n

How Cataligent Helps Through CAT4<\/h2>\n

Cataligent helps enterprises and consulting firms move beyond manual reporting by connecting business model execution to CAT4, its no code strategy execution platform. Cataligent supports the business design and configuration side, while CAT4 provides the governed platform for initiatives, approvals, value tracking, workflows, and executive reporting.<\/p>\n

Inside CAT4, a business model can be translated into a controlled hierarchy of Organization, Portfolio, Program, Project, Measure Package, and Measure. This hierarchy helps teams connect broad business model choices to practical units of work. A new market model can become programs, projects, and measures with owners, milestones, dependencies, financial effects, and closure rules.<\/p>\n

CAT4’s Degree of Implementation, or DoI, helps teams track whether a measure is defined, identified, detailed, decided, implemented, or closed. This gives leaders a stronger view than a manual percent complete field. CAT4 also separates Implementation Status and Potential Status, which helps show whether work is progressing and whether expected value is still credible.<\/p>\n

For savings initiatives<\/a>, this structure can connect baseline, target, forecast, actuals, approvals, and controller validation. For consulting firms, it can reduce the effort spent rebuilding status decks and give client teams a repeatable execution layer for complex engagements.<\/p>\n

Cataligent has 25 years in continuous operation since 2000, with 250+ large enterprise installations and 40,000+ users worldwide. Those facts matter because moving away from manual reporting requires enterprise level execution control, not only a better spreadsheet.<\/p>\n

How to move from manual reporting to business model control<\/h2>\n

Start by reviewing the current manual report and marking every field that is a governance item rather than a presentation item. Owner, sponsor, approval status, risk, dependency, forecast value, actual value, and closure evidence should not live only in a reporting file. They should be part of the execution system.<\/p>\n

Next, define the value logic of the business model. What is the baseline? What is the target? What must happen before value can be forecast? What evidence is needed before value is accepted as actual? Who confirms the result? These questions turn business model design into measurable execution.<\/p>\n

Finally, redesign the reporting cadence around decisions. A report should show what changed, what is blocked, what value is at risk, and what decision leaders need to make. If the report cannot trigger decisions, it is not supporting the business model strongly enough.<\/p>\n

Conclusion<\/h2>\n

Developing a business model and producing manual reporting are not the same discipline. A business model needs execution structure, governance, value tracking, and closure criteria. Manual reporting can describe activity, but it cannot replace controlled execution.<\/p>\n

If your team is managing a new business model through spreadsheets and slide decks, Cataligent can help you design a governed execution layer through CAT4. The right first step is to identify which parts of the report should become controlled workflow, approval, and value tracking data.<\/p>\n

FAQs<\/h2>\n

Q: Why is manual reporting risky for business model execution?<\/h3>\n

Manual reporting can separate ownership, approvals, value tracking, and decision history across files and emails. This makes it harder for leaders to know whether the business model is being executed with control.<\/p>\n

Q: What should teams define before building reports?<\/h3>\n

Teams should define the work hierarchy, owners, sponsors, financial logic, approval gates, dependencies, reporting cadence, and closure criteria. These items create the execution structure that reports should reflect.<\/p>\n

Q: How does Cataligent help teams move beyond manual reporting through CAT4?<\/h3>\n

Cataligent helps teams translate business model choices into governed initiatives, measures, workflows, and reports through CAT4. CAT4 supports hierarchy, DoI stage gates, Implementation Status, Potential Status, financial tracking, and controller backed closure.<\/p>\n","protected":false},"excerpt":{"rendered":"

Developing Business Model vs Manual Reporting: What Teams Should Know Developing business model logic and producing manual reporting are often treated as connected tasks, but they solve different problems. A business model explains how value will be created, delivered, and measured. Manual reporting tries to describe what happened after work begins. When teams confuse the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2104],"tags":[2033,568,632,1739,2107,1967,2106,2105],"class_list":["post-5783","post","type-post","status-publish","format-standard","hentry","category-strategy-planning","tag-business-strategy","tag-cost-reduction-strategies","tag-cost-reduction-strategy","tag-digital-strategy","tag-planning","tag-strategic-decision-making","tag-strategic-planning","tag-strategy-planning"],"yoast_head":"\nDeveloping Business Model vs Manual Reporting: What Teams Should Know - Cataligent<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cataligent.in\/blog\/strategy-planning\/developing-business-model-vs-manual-reporting-what-teams-should-know\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Developing Business Model vs Manual Reporting: What Teams Should Know - Cataligent\" \/>\n<meta property=\"og:description\" content=\"Developing Business Model vs Manual Reporting: What Teams Should Know Developing business model logic and producing manual reporting are often treated as connected tasks, but they solve different problems. A business model explains how value will be created, delivered, and measured. Manual reporting tries to describe what happened after work begins. When teams confuse the […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cataligent.in\/blog\/strategy-planning\/developing-business-model-vs-manual-reporting-what-teams-should-know\/\" \/>\n<meta property=\"og:site_name\" content=\"Cataligent\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/Cataligentstrategyimplementation\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-04-16T14:01:02+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-10T11:37:44+00:00\" \/>\n<meta name=\"author\" content=\"cat_admin_usr\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@cataligentindia\" \/>\n<meta name=\"twitter:site\" content=\"@cataligentindia\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"cat_admin_usr\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/developing-business-model-vs-manual-reporting-what-teams-should-know\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/developing-business-model-vs-manual-reporting-what-teams-should-know\\\/\"},\"author\":{\"name\":\"cat_admin_usr\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#\\\/schema\\\/person\\\/649c37d6027e076e1e76bd18bac05756\"},\"headline\":\"Developing Business Model vs Manual Reporting: What Teams Should Know\",\"datePublished\":\"2026-04-16T14:01:02+00:00\",\"dateModified\":\"2026-06-10T11:37:44+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/developing-business-model-vs-manual-reporting-what-teams-should-know\\\/\"},\"wordCount\":1476,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#organization\"},\"keywords\":[\"Business Strategy\",\"Cost Reduction Strategies\",\"Cost Reduction Strategy\",\"Digital Strategy\",\"Planning\",\"Strategic Decision-Making\",\"Strategic Planning\",\"Strategy Planning\"],\"articleSection\":[\"Strategy Planning\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/developing-business-model-vs-manual-reporting-what-teams-should-know\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/developing-business-model-vs-manual-reporting-what-teams-should-know\\\/\",\"url\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/developing-business-model-vs-manual-reporting-what-teams-should-know\\\/\",\"name\":\"Developing Business Model vs Manual Reporting: What Teams Should Know - Cataligent\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#website\"},\"datePublished\":\"2026-04-16T14:01:02+00:00\",\"dateModified\":\"2026-06-10T11:37:44+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/developing-business-model-vs-manual-reporting-what-teams-should-know\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/developing-business-model-vs-manual-reporting-what-teams-should-know\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/strategy-planning\\\/developing-business-model-vs-manual-reporting-what-teams-should-know\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Developing Business Model vs Manual Reporting: What Teams Should Know\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/\",\"name\":\"https:\\\/\\\/cataligent.in\\\/\",\"description\":\"Strategy Execution Tool for Cost Saving Program\",\"publisher\":{\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#organization\",\"name\":\"Cataligent Project Pvt. Ltd.\",\"url\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/01\\\/logoColored-1.png\",\"contentUrl\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/01\\\/logoColored-1.png\",\"width\":296,\"height\":75,\"caption\":\"Cataligent Project Pvt. Ltd.\"},\"image\":{\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/Cataligentstrategyimplementation\\\/\",\"https:\\\/\\\/x.com\\\/cataligentindia\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/cataligentstrategy\\\/\",\"https:\\\/\\\/www.instagram.com\\\/cataligentindia\\\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/#\\\/schema\\\/person\\\/649c37d6027e076e1e76bd18bac05756\",\"name\":\"cat_admin_usr\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5a61f472589fc237202ca132bc60e152f3e6a99196f2e24dcf2a5f01626f1b4a?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5a61f472589fc237202ca132bc60e152f3e6a99196f2e24dcf2a5f01626f1b4a?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5a61f472589fc237202ca132bc60e152f3e6a99196f2e24dcf2a5f01626f1b4a?s=96&d=mm&r=g\",\"caption\":\"cat_admin_usr\"},\"sameAs\":[\"https:\\\/\\\/cataligent.in\\\/blog\"],\"url\":\"https:\\\/\\\/cataligent.in\\\/blog\\\/author\\\/cat_admin_usr\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Developing Business Model vs Manual Reporting: What Teams Should Know - Cataligent","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cataligent.in\/blog\/strategy-planning\/developing-business-model-vs-manual-reporting-what-teams-should-know\/","og_locale":"en_US","og_type":"article","og_title":"Developing Business Model vs Manual Reporting: What Teams Should Know - Cataligent","og_description":"Developing Business Model vs Manual Reporting: What Teams Should Know Developing business model logic and producing manual reporting are often treated as connected tasks, but they solve different problems. A business model explains how value will be created, delivered, and measured. Manual reporting tries to describe what happened after work begins. When teams confuse the […]","og_url":"https:\/\/cataligent.in\/blog\/strategy-planning\/developing-business-model-vs-manual-reporting-what-teams-should-know\/","og_site_name":"Cataligent","article_publisher":"https:\/\/www.facebook.com\/Cataligentstrategyimplementation\/","article_published_time":"2026-04-16T14:01:02+00:00","article_modified_time":"2026-06-10T11:37:44+00:00","author":"cat_admin_usr","twitter_card":"summary_large_image","twitter_creator":"@cataligentindia","twitter_site":"@cataligentindia","twitter_misc":{"Written by":"cat_admin_usr","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/cataligent.in\/blog\/strategy-planning\/developing-business-model-vs-manual-reporting-what-teams-should-know\/#article","isPartOf":{"@id":"https:\/\/cataligent.in\/blog\/strategy-planning\/developing-business-model-vs-manual-reporting-what-teams-should-know\/"},"author":{"name":"cat_admin_usr","@id":"https:\/\/cataligent.in\/blog\/#\/schema\/person\/649c37d6027e076e1e76bd18bac05756"},"headline":"Developing Business Model vs Manual Reporting: What Teams Should Know","datePublished":"2026-04-16T14:01:02+00:00","dateModified":"2026-06-10T11:37:44+00:00","mainEntityOfPage":{"@id":"https:\/\/cataligent.in\/blog\/strategy-planning\/developing-business-model-vs-manual-reporting-what-teams-should-know\/"},"wordCount":1476,"commentCount":0,"publisher":{"@id":"https:\/\/cataligent.in\/blog\/#organization"},"keywords":["Business Strategy","Cost Reduction Strategies","Cost Reduction Strategy","Digital Strategy","Planning","Strategic Decision-Making","Strategic Planning","Strategy Planning"],"articleSection":["Strategy Planning"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/cataligent.in\/blog\/strategy-planning\/developing-business-model-vs-manual-reporting-what-teams-should-know\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/cataligent.in\/blog\/strategy-planning\/developing-business-model-vs-manual-reporting-what-teams-should-know\/","url":"https:\/\/cataligent.in\/blog\/strategy-planning\/developing-business-model-vs-manual-reporting-what-teams-should-know\/","name":"Developing Business Model vs Manual Reporting: What Teams Should Know - Cataligent","isPartOf":{"@id":"https:\/\/cataligent.in\/blog\/#website"},"datePublished":"2026-04-16T14:01:02+00:00","dateModified":"2026-06-10T11:37:44+00:00","breadcrumb":{"@id":"https:\/\/cataligent.in\/blog\/strategy-planning\/developing-business-model-vs-manual-reporting-what-teams-should-know\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cataligent.in\/blog\/strategy-planning\/developing-business-model-vs-manual-reporting-what-teams-should-know\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cataligent.in\/blog\/strategy-planning\/developing-business-model-vs-manual-reporting-what-teams-should-know\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cataligent.in\/blog\/"},{"@type":"ListItem","position":2,"name":"Developing Business Model vs Manual Reporting: What Teams Should Know"}]},{"@type":"WebSite","@id":"https:\/\/cataligent.in\/blog\/#website","url":"https:\/\/cataligent.in\/blog\/","name":"https:\/\/cataligent.in\/","description":"Strategy Execution Tool for Cost Saving Program","publisher":{"@id":"https:\/\/cataligent.in\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cataligent.in\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/cataligent.in\/blog\/#organization","name":"Cataligent Project Pvt. Ltd.","url":"https:\/\/cataligent.in\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/cataligent.in\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/cataligent.in\/blog\/wp-content\/uploads\/2025\/01\/logoColored-1.png","contentUrl":"https:\/\/cataligent.in\/blog\/wp-content\/uploads\/2025\/01\/logoColored-1.png","width":296,"height":75,"caption":"Cataligent Project Pvt. Ltd."},"image":{"@id":"https:\/\/cataligent.in\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/Cataligentstrategyimplementation\/","https:\/\/x.com\/cataligentindia","https:\/\/www.linkedin.com\/company\/cataligentstrategy\/","https:\/\/www.instagram.com\/cataligentindia\/"]},{"@type":"Person","@id":"https:\/\/cataligent.in\/blog\/#\/schema\/person\/649c37d6027e076e1e76bd18bac05756","name":"cat_admin_usr","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/5a61f472589fc237202ca132bc60e152f3e6a99196f2e24dcf2a5f01626f1b4a?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/5a61f472589fc237202ca132bc60e152f3e6a99196f2e24dcf2a5f01626f1b4a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5a61f472589fc237202ca132bc60e152f3e6a99196f2e24dcf2a5f01626f1b4a?s=96&d=mm&r=g","caption":"cat_admin_usr"},"sameAs":["https:\/\/cataligent.in\/blog"],"url":"https:\/\/cataligent.in\/blog\/author\/cat_admin_usr\/"}]}},"_links":{"self":[{"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/posts\/5783","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/comments?post=5783"}],"version-history":[{"count":0,"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/posts\/5783\/revisions"}],"wp:attachment":[{"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/media?parent=5783"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/categories?post=5783"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cataligent.in\/blog\/wp-json\/wp\/v2\/tags?post=5783"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}