{"id":179,"date":"2026-05-26T11:30:00","date_gmt":"2026-05-26T03:30:00","guid":{"rendered":"https:\/\/imtiajwrites.com\/blog\/?p=179"},"modified":"2026-05-26T18:58:45","modified_gmt":"2026-05-26T10:58:45","slug":"non-native-copywriter-portfolio-proof","status":"publish","type":"post","link":"https:\/\/imtiajwrites.com\/blog\/non-native-copywriter-portfolio-proof\/","title":{"rendered":"The Portfolio Move That Beats a Native-Speaker Writer: Proof Over Polish"},"content":{"rendered":"\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\">Your non-native copywriter portfolio is competing in the wrong category. You&#8217;ve probably felt this without naming it. You send three samples. The client comes back two days later saying they &#8220;went with someone else who felt like a better fit.&#8221; You don&#8217;t ask what <em>fit<\/em> meant. You already suspect.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Here&#8217;s what&#8217;s actually happening on the other side of that decision.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The client opened your portfolio. The samples were clean. The grammar was right. But the writing felt slightly less effortless than the native applicant&#8217;s, and the brain registered that as risk. Not consciously. Not in a way the client could articulate if you asked. Just enough to tip a 50-50 call to the other person.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can fight that fight on fluency. You will lose, often. Or you can change what the portfolio is being judged on. This post is about the second move.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>You&#8217;ve probably received feedback like this<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Imagine the brief lands in your inbox. The client wants three writing samples and &#8220;a bit about your previous results.&#8221; You send the samples. You write a paragraph about results. You hear nothing for five days. Then a polite no.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The mistake isn&#8217;t in any single sample. The mistake is structural. A portfolio that leads with writing samples invites the client to evaluate writing. Once writing is the criterion, fluency becomes the tiebreaker, and a native writer wins the tiebreaker on average. Not always. On average.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A portfolio that leads with <em>outcomes<\/em> invites the client to evaluate business results. Once business results are the criterion, the question stops being &#8220;who sounds more native&#8221; and becomes &#8220;who can I trust to move my numbers.&#8221; That&#8217;s a fight you can win.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The reframe sounds obvious when written down. Almost nobody does it. That&#8217;s the opportunity.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" data-src=\"https:\/\/imtiajwrites.com\/wp-content\/uploads\/2026\/05\/proof-stack-non-native-copywriter-portfolio.svg\" alt=\"\" class=\"wp-image-180 lazyload\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The data says proof works<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Two findings worth knowing before you restructure anything.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">First, from Sopro&#8217;s 2025 B2B buyer survey: 69% of B2B marketers consider case studies their most effective form of content (<a href=\"https:\/\/sopro.io\/resources\/blog\/b2b-buyer-statistics-and-insights\/\" target=\"_blank\" rel=\"noopener\">Sopro<\/a>). Buyers ranked them among the top three formats they actually want from vendors. That&#8217;s not a marketing-side preference. That&#8217;s the buyer side telling you what they read.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Second, also from the Sopro survey: 77% of B2B buyers consult user reviews during their purchasing journey, and 54% speak directly with current users before purchasing. The decision-makers hiring you are research-heavy. They&#8217;re not reading your prose to decide. They&#8217;re reading your proof.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What this means for a non-native copywriter portfolio is straightforward. The clients you actually want to work with are already trained to value evidence over polish. You&#8217;re not asking them to change their behaviour. You&#8217;re meeting them where they already are.<\/p>\n\n\n\n<div class=\"beehiiv-form-wrap\">\n  <script async src=\"https:\/\/subscribe-forms.beehiiv.com\/v3\/loader.js\" data-beehiiv-form=\"c6123e0f-d115-4142-9528-a464c2850fcc\"><\/script>\n\n  <script type=\"text\/javascript\" async src=\"https:\/\/subscribe-forms.beehiiv.com\/attribution.js\"><\/script>\n<\/div>\n\n<style>\n  .beehiiv-form-wrap {\n    width: 100%;\n    overflow: visible;\n    margin-bottom: 32px;\n  }\n\n  .beehiiv-form-wrap iframe {\n    display: block;\n    width: 100% !important;\n    height: auto !important;\n    min-height: 360px !important;\n    overflow: visible !important;\n  }\n<\/style>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The framework: The Proof Stack<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When you restructure your non-native copywriter portfolio around proof, every project entry follows the same three-layer pattern. Call this <strong>The Proof Stack<\/strong>:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">1. <strong>Outcome.<\/strong> What measurable thing changed because of the work? Conversion lift, revenue, signups, traffic, retention, time-to-publish, support ticket reduction. One number, named clearly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">2. <strong>Approach.<\/strong> What was the strategic call you made that produced the outcome? Two or three sentences, no fluff, no generic copywriter vocabulary.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">3. <strong>Evidence.<\/strong> What can the prospect actually verify? A live URL, a screenshot, a testimonial with a name and role, before\/after copy, an analytics screen, a published byline.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Outcome answers <em>what<\/em>. Approach answers <em>why<\/em>. Evidence answers <em>how do I know you didn&#8217;t make this up<\/em>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A native writer&#8217;s portfolio often skips Outcome and Evidence entirely, because the writing itself is the implied proof. You can&#8217;t afford that move. Your Proof Stack has to do the work that fluency does for them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Now the rebuild.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Layer 1: Lead with the outcome, not the sample<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The single highest-leverage edit you can make to your portfolio in the next hour is reordering the page.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u274c <em>Sample 1: Email sequence for a Series B SaaS. [Read the copy.]<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u2705 <em>Increased trial-to-paid conversion 24% for a Series B SaaS. [See the email sequence and the analytics screen that proves it.]<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The native applicant&#8217;s portfolio almost certainly leads with the sample. When yours leads with the outcome, the comparison frame inverts before the client has read a single word of copy. You&#8217;re not &#8220;the non-native writer with the writing samples.&#8221; You&#8217;re &#8220;the writer with the 24% conversion lift.&#8221; The client now has to hire the <em>other<\/em> person despite that anchor, instead of hiring you despite something.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you don&#8217;t have hard numbers from past clients, you have two real options. One: ask. Most clients will share if you ask warmly and explain the context (an email like <em>&#8220;I&#8217;m refining how I describe this project on my site. Did the sequence end up moving the conversion number? Even a rough sense would help.&#8221;<\/em> gets answers more often than not). Two: rebuild a project as a spec and run it through your own list, your own LinkedIn, or a pro-bono client, then track the result honestly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What you don&#8217;t do is invent numbers. Anything fabricated will eventually surface in a discovery call when the client asks a follow-up question, and the conversation ends three sentences after that.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Layer 2: Approach as proof of thinking<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This is the layer most non-native copywriters get wrong, and it&#8217;s where the leverage actually compounds.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Approach is not a description of what you wrote. It&#8217;s a description of what you <em>decided<\/em>. The decision is what the client is hiring. The writing is the artefact.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u274c <em>I wrote a five-email welcome sequence with strong subject lines and clear CTAs.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u2705 <em>The previous welcome sequence pushed for the upgrade in email two. I moved the upgrade ask to email four and used emails one through three to surface the customer&#8217;s own usage data back to them. The thesis: people upgrade when they realise they&#8217;re already using the product enough to justify the cost, not when a stranger tells them to.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The second version isn&#8217;t longer because it&#8217;s wordier. It&#8217;s longer because it has content. It tells the client you can think about <em>why<\/em> a sequence works, not just <em>that<\/em> you can write one. That positions you above 90% of the freelance market, native or not, because most copywriter portfolios skip the <em>why<\/em> entirely.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Specificity is what makes Approach hard to fake. A generic &#8220;I focused on customer-centric messaging and clear value propositions&#8221; reads like every other portfolio on the internet. A specific decision (&#8220;I moved the upgrade ask to email four because&#8230;&#8221;) could only come from someone who actually did the work.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is also where your non-native lens stops being a liability and starts being a feature. If you&#8217;re writing for a Western audience from inside a non-Western market, you&#8217;ve probably noticed framing decisions a native writer wouldn&#8217;t notice. Name them. <em>&#8220;The original copy used a sports analogy. The brand has 40% non-US users, many of whom don&#8217;t share that reference, so I rewrote with a more universally legible metaphor.&#8221;<\/em> That single sentence is worth more than three pages of fluent prose, because no native writer in the same applicant pool is making that observation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For more on how this kind of cross-cultural framing becomes a paid skill rather than an apology, see <a href=\"https:\/\/imtiajwrites.com\/write-copy-for-global-brands\">the post on writing copy for global brands<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Layer 3: Evidence the client can verify in 10 seconds<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The third layer is what stops every previous claim from being just claims.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A live URL beats a screenshot. A screenshot beats a description. A testimonial with a name, role, company, and ideally a photo beats an anonymous quote. An analytics view (even with sensitive numbers blurred) beats &#8220;the campaign performed well.&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Some of the strongest portfolios in the freelance market right now use a simple pattern at the bottom of every project: a small grid with three or four verification items.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>LIVE: client-domain.com\/landing-page\nRESULT: 24% lift in trial-to-paid (May to August)\nTESTIMONIAL: Sarah K., Head of Growth (linked LinkedIn profile)\nSAMPLES: 3 emails from the sequence (rendered in-page)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">That block takes about 90 seconds to read and gives the prospect everything they need to decide whether to set up a call. It also does something quieter: it tells the prospect you&#8217;re the kind of person who organises information clearly, which is the actual job they&#8217;re hiring for.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you don&#8217;t have live URLs because past clients are under NDA, two reasonable workarounds. First, ask permission to show anonymised versions (&#8220;Acme Inc., a Series B SaaS in [industry], 80\u2013120 employees&#8221; beats no context at all). Second, build one new spec project per quarter that <em>can<\/em> be public, and rotate it into the portfolio.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What you do with the writing samples themselves<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">You don&#8217;t delete them. You demote them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The samples now live underneath The Proof Stack on each project, not above it. The client encounters the outcome, reads the approach, scans the evidence, and then <em>if interested<\/em> clicks through to the actual copy. By the time they read the prose, they&#8217;ve already decided you&#8217;re worth taking seriously, which means small naturalness imperfections in your sentences register completely differently than they would on a cold first read.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This isn&#8217;t a trick. It&#8217;s a sequencing decision that uses how attention actually works. Once a reader has decided to invest interest in someone, they read more generously. The fluency gap that would have been a tiebreaker against you on a cold portfolio becomes a non-issue on a warm one.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For more on the broader trust-gap dynamics behind why this sequencing matters specifically for non-native applicants, the <a href=\"https:\/\/imtiajwrites.com\/country-of-origin-trust-gap\">country-of-origin trust gap post<\/a> covers the underlying mechanics.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>A note on what <em>not<\/em> to do<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Three traps worth flagging before they cost you a project.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">First: don&#8217;t apologise for being non-native anywhere on the portfolio. Not in the bio, not in the about page, not in the cover note. The client doesn&#8217;t need the disclosure, and offering it primes the exact comparison frame you&#8217;re trying to escape. Let the work speak. If it comes up in conversation, handle it then, with confidence.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Second: don&#8217;t pad. A portfolio with three strong Proof Stacks beats one with eight half-built ones. Quality of evidence outranks quantity of samples every time, especially when the prospect is comparing you to someone with a higher native-fluency baseline. Every weak entry pulls the average down.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Third: don&#8217;t price low to compensate. Pricing low to offset a perceived non-native discount communicates exactly the thing you want the portfolio to refute. If your work moves numbers, charge what work that moves numbers costs. The full reasoning is in the <a href=\"https:\/\/imtiajwrites.com\/non-native-copywriter-pricing\">non-native copywriter pricing post<\/a>, but the short version is: a portfolio that leads with proof and a price that signals confidence are the same move expressed two different ways.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Where to go next<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u2192 If portfolio structure is the bottleneck right now, the rebuild order is: pick your three strongest projects, write the Outcome line for each, write the Approach paragraph for each, gather the Evidence for each, then publish the page. The whole rebuild is usually a weekend.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u2192 If pricing is the next conversation after a client has seen a proof-led portfolio, <a href=\"https:\/\/imtiajwrites.com\/non-native-copywriter-pricing\">the non-native copywriter pricing post<\/a> covers how to set rates that match the proof.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u2192 If you want the broader system behind writing professional English at the level the proof-led portfolio implies, the <a href=\"https:\/\/imtiajwrites.beehiiv.com\" target=\"_blank\" rel=\"noopener\">Natural English Edit<\/a> is the diagnostic that runs on the writing itself: fifteen patterns with the ChatGPT prompts to catch them on your own copy. Free.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The portfolio that beats a native writer isn&#8217;t the one with smoother prose. It&#8217;s the one that changes what&#8217;s being measured.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Frequently Asked Questions<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why does a non-native copywriter portfolio need a different structure than a native writer&#8217;s?<\/strong> Because the default portfolio structure (samples first) invites the client to judge fluency. On fluency, native writers win the tiebreaker on average. A proof-first structure changes the criterion to business outcomes, where non-native writers can compete and often win. The framework matters more than the prose.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What is The Proof Stack?<\/strong> A three-layer pattern for every portfolio entry: Outcome (the measurable result), Approach (the strategic decision behind the result), and Evidence (something the client can verify in under a minute). Outcome answers <em>what<\/em>. Approach answers <em>why<\/em>. Evidence answers <em>how do I know it&#8217;s real<\/em>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What if I don&#8217;t have measurable results from past clients?<\/strong> Two real options. One, ask past clients warmly. Most will share rough numbers if you explain the context. Two, build a spec project, run it through your own list or LinkedIn, and track real numbers honestly. What you don&#8217;t do is invent figures. Fabricated results surface in discovery calls and end the conversation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Should I tell clients I&#8217;m a non-native English speaker on my portfolio?<\/strong> No. Don&#8217;t put it in the bio, the about page, or the cover note. Disclosure primes the exact fluency comparison the proof-led structure is designed to bypass. If the topic comes up in a call, address it confidently then. Otherwise let the proof do the work.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How many projects should a non-native copywriter portfolio show?<\/strong> Three to five strong Proof Stacks beats eight half-built ones. Every weak entry lowers the perceived quality of the portfolio average. Quality of evidence outranks quantity of samples, particularly when the prospect is comparing you to a native applicant with higher baseline fluency.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Does this strategy work for beginner non-native copywriters with no client results yet?<\/strong> Yes, with one adjustment. If you don&#8217;t have client outcomes, the Outcome layer becomes &#8220;what I tested and what I learned&#8221; rather than &#8220;what I produced.&#8221; Build two or three spec projects, run them in any traffic environment you have access to, and report the results honestly. The structure (Outcome, Approach, Evidence) is the same. Only the source of the data changes.<\/p>\n\n\n\n<script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@graph\": [\n    {\n      \"@type\": \"Article\",\n      \"headline\": \"The Portfolio Move That Beats a Native-Speaker Writer: Proof Over Polish\",\n      \"description\": \"Non-native copywriter portfolio strategy that wins clients native writers won't. Trade fluency polish for proof of results. The Proof Stack framework, in full.\",\n      \"author\": {\n        \"@type\": \"Person\",\n        \"name\": \"Imtiaj Choudhury\",\n        \"url\": \"https:\/\/imtiajwrites.com\"\n      },\n      \"publisher\": {\n        \"@type\": \"Organization\",\n        \"name\": \"ImtiajWrites\",\n        \"url\": \"https:\/\/imtiajwrites.com\"\n      },\n      \"url\": \"https:\/\/imtiajwrites.com\/non-native-copywriter-portfolio-proof\",\n      \"mainEntityOfPage\": \"https:\/\/imtiajwrites.com\/non-native-copywriter-portfolio-proof\",\n      \"inLanguage\": \"en\",\n      \"datePublished\": \"2026-05-07\",\n      \"dateModified\": \"2026-05-07\",\n      \"articleSection\": \"Turning Skill Into Income\",\n      \"keywords\": \"non-native copywriter portfolio, portfolio strategy for non-native writers, how to win clients as a non-native writer, case study portfolio for copywriters, competing with native English writers\"\n    },\n    {\n      \"@type\": \"FAQPage\",\n      \"mainEntity\": [\n        {\n          \"@type\": \"Question\",\n          \"name\": \"Why does a non-native copywriter portfolio need a different structure than a native writer's?\",\n          \"acceptedAnswer\": {\n            \"@type\": \"Answer\",\n            \"text\": \"Because the default portfolio structure (samples first) invites the client to judge fluency. On fluency, native writers win the tiebreaker on average. A proof-first structure changes the criterion to business outcomes, where non-native writers can compete and often win. The framework matters more than the prose.\"\n          }\n        },\n        {\n          \"@type\": \"Question\",\n          \"name\": \"What is The Proof Stack?\",\n          \"acceptedAnswer\": {\n            \"@type\": \"Answer\",\n            \"text\": \"A three-layer pattern for every portfolio entry: Outcome (the measurable result), Approach (the strategic decision behind the result), and Evidence (something the client can verify in under a minute). Outcome answers what. Approach answers why. Evidence answers how do I know it's real.\"\n          }\n        },\n        {\n          \"@type\": \"Question\",\n          \"name\": \"What if I don't have measurable results from past clients?\",\n          \"acceptedAnswer\": {\n            \"@type\": \"Answer\",\n            \"text\": \"Two real options. One, ask past clients warmly. Most will share rough numbers if you explain the context. Two, build a spec project, run it through your own list or LinkedIn, and track real numbers honestly. What you don't do is invent figures. Fabricated results surface in discovery calls and end the conversation.\"\n          }\n        },\n        {\n          \"@type\": \"Question\",\n          \"name\": \"Should I tell clients I'm a non-native English speaker on my portfolio?\",\n          \"acceptedAnswer\": {\n            \"@type\": \"Answer\",\n            \"text\": \"No. Don't put it in the bio, the about page, or the cover note. Disclosure primes the exact fluency comparison the proof-led structure is designed to bypass. If the topic comes up in a call, address it confidently then. Otherwise let the proof do the work.\"\n          }\n        },\n        {\n          \"@type\": \"Question\",\n          \"name\": \"How many projects should a non-native copywriter portfolio show?\",\n          \"acceptedAnswer\": {\n            \"@type\": \"Answer\",\n            \"text\": \"Three to five strong Proof Stacks beats eight half-built ones. Every weak entry lowers the perceived quality of the portfolio average. Quality of evidence outranks quantity of samples, particularly when the prospect is comparing you to a native applicant with higher baseline fluency.\"\n          }\n        },\n        {\n          \"@type\": \"Question\",\n          \"name\": \"Does this strategy work for beginner non-native copywriters with no client results yet?\",\n          \"acceptedAnswer\": {\n            \"@type\": \"Answer\",\n            \"text\": \"Yes, with one adjustment. If you don't have client outcomes, the Outcome layer becomes 'what I tested and what I learned' rather than 'what I produced.' Build two or three spec projects, run them in any traffic environment you have access to, and report the results honestly. The structure (Outcome, Approach, Evidence) is the same. Only the source of the data changes.\"\n          }\n        }\n      ]\n    }\n  ]\n}\n<\/script>\n","protected":false},"excerpt":{"rendered":"<p>A native writer&#8217;s portfolio sells fluency. You can&#8217;t win that fight, and you don&#8217;t need to. Replace polish with proof and the comparison stops being about who sounds more native. The Proof Stack framework, in full.<\/p>\n","protected":false},"author":1,"featured_media":180,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[37],"tags":[81,82,50,52,80],"class_list":["post-179","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-turning-skill-into-income","tag-case-studies","tag-client-acquisition","tag-freelance-copywriting","tag-non-native-writers","tag-portfolio-strategy"],"blocksy_meta":[],"_links":{"self":[{"href":"https:\/\/imtiajwrites.com\/blog\/wp-json\/wp\/v2\/posts\/179","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/imtiajwrites.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/imtiajwrites.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/imtiajwrites.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/imtiajwrites.com\/blog\/wp-json\/wp\/v2\/comments?post=179"}],"version-history":[{"count":4,"href":"https:\/\/imtiajwrites.com\/blog\/wp-json\/wp\/v2\/posts\/179\/revisions"}],"predecessor-version":[{"id":299,"href":"https:\/\/imtiajwrites.com\/blog\/wp-json\/wp\/v2\/posts\/179\/revisions\/299"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/imtiajwrites.com\/blog\/wp-json\/wp\/v2\/media\/180"}],"wp:attachment":[{"href":"https:\/\/imtiajwrites.com\/blog\/wp-json\/wp\/v2\/media?parent=179"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/imtiajwrites.com\/blog\/wp-json\/wp\/v2\/categories?post=179"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/imtiajwrites.com\/blog\/wp-json\/wp\/v2\/tags?post=179"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}