NFNicolas Ferro
Portrait of Nicolas Ferro

Nicolas FerroOperations & strategy · English and Spanish

I organize the evidence teams use to make decisions.

I built a bilingual data room, found and fixed errors in a 48-month financial model, and turned policy research into briefs.

From the data-room case

What was ready to update?

A 41-page revision packet arrived while a new financial model was still pending. I gave the team a page-by-page brief showing which edits could proceed and which figures had to wait.

Update now

Replace the executive summary in English and Spanish. Leave unrelated sections intact.

Hold for approval

Don’t update figures in the summaries, charts, or tooltips until the new model is approved.

Released

Once the team signed off on the figures, I updated the tables and published both versions.

Selected Work

Featured case / Data-room setup & change governance

Building and publishing
a bilingual data room.

A revised forecast could change a table, a chart and the figures in an executive summary. Those changes had to agree in English and Spanish.

My contribution: I owned the layout, changes and publication. Across several rounds, I revised the pages and tables using figures that multiple people on the team had approved.

Work produced

The published data room in both languages and a page-by-page brief for revisions.

Explore the data-room decisions

How I built it

Separate operating forecasts from funding materials.

I set up the bilingual data room around how people would use it. Ongoing forecasts and reporting belonged together; investment materials needed their own section so readers could find the funding story without digging through operating updates.

Illustrative structure with fictional file names

  • Operating forecasts
    • Operating model
    • Monthly reporting summary
  • Funding materials
    • Funding overview
    • Use-of-funds summary

Example review check: When the forecast changes, trace any affected summary figures back to the approved model and check the same values in both languages before release.

Where the judgment mattered

Do not execute the whole packet blindly

A 41-page revision packet arrived while a new financial model and business direction were pending. I separated edits that could proceed from those that would become obsolete, rather than treating every suggestion as an instruction.

Check the workbook preview

A reviewer could not open a workbook preview. I verified that the preview worked and traced the problem to the review tool’s access.

Match detail to the change

I replaced the executive summary where only the text needed changing and reworked the layout on the page that needed a new structure. The brief also covered language switching and translated content, rather than assuming one-language edits were complete.

Protect the boundary

I explicitly excluded private negotiation context from the site update and required calculation review before implementation. Technical development-plan corrections remained with the technical owner.

One change, from decision to handoff

Composite reconstruction of documented decisions across several reviews. The checklist illustrates handoff requirements, not a completed acceptance test.

Decision

Update the executive narrative now, but hold model-dependent numbers until the new financial source is approved. Rebuild only the section that needs a new structure.

Artifact: scoped change brief

Executive overview

Replace the agreed summary text. Keep the rest of the page unchanged. Supply the corresponding Spanish text.

Detailed section

Specify the revised content hierarchy and expandable cards. Identify the exact page and language-switching behavior.

Financial content

List affected cards, charts and tooltips. Mark model-dependent content “awaiting approved source” rather than copying stale figures.

Review boundary

Exclude private negotiation context. Route technical-plan changes to the technical owner. Check a reported preview problem separately from the requested layout changes.

Handoff

Apply the agreed edits in both languages. Leave unresolved financial and technical questions with the people responsible for them.

Review

Check the changed text against its source, reconcile charts and tooltips, compare language versions and confirm that untouched sections remained intact.

Interactive reconstruction

Which changes are safe to release?

Take a proposed change from source review to bilingual release.

The handoff includes continuity

Questions for a migration

I raised transfer completion, former-platform availability, access requests and maintenance messaging with the responsible technical owners.

My role in the handoff

I managed changes to the data room and published each revision after the relevant approvals. The technical team handled infrastructure decisions.

Back to cases

The implementation brief
for the Showcase.

The Showcase combined film, music and an interactive teaser. Bringing those pieces together required decisions about assets, integration, measurement and mobile performance.

My role: I gathered requirements and wrote the implementation brief, including what assets were needed and who would make the technical decisions.

Work delivered

The team used my brief to build the Showcase and refined it over several iterations.

Explore the planning brief

Anonymized reconstruction of actual planning work

Follow the interactive teaser from request to handoff

Statuses shown at handoff, before implementation.
Project and people generalized.

Back to cases

Finding and fixing errors
in a 48-month forecast.

Forecast periods, formula references and summary figures did not always agree.

My role: I traced discrepancies in Excel, corrected some myself and coordinated the remaining fixes. I took questions about budget scope and metric definitions to management.

Work delivered

A record of corrected ranges and references, with unresolved budget and metric questions listed separately.

Explore the forecast review

How the model works

Turn a runway estimate into something you can check.

Change the revenue assumption to see how it affects estimated runway with the same cost base.

Illustrative model with fictional figures

Starting cash
$480,000
Monthly costs
$60,000
Monthly net burn
$60,000
Estimated runway
8 months

Logic: Starting cash ÷ (monthly costs − monthly revenue). This example holds monthly amounts constant; the detailed forecast below illustrates why a model with changing costs needs its period ranges and summary references checked separately.

Reconstructed cases / Illustrative figures

Trace a forecast discrepancy

Real issue patterns and recorded outcomes.
Example units replace company figures.

Additional case: clarifying a financial metric

Management handoff

Different findings need different next actions.

FindingRecorded statusNext action
F01 · Period coverageCorrection appliedRetain the changed range and dependent views in the review record.
F02 · Summary referencesCorrection appliedKeep the mapping from detailed schedules to the summary.
F03 · Budget overlapTeam decision requiredConfirm scope before changing the cost base.
F04 · Metric meaningDefinition to clarifyAgree the intended measure and its required inputs.
Back to cases

Setting up Zoho CRM
for team outreach.

The team used the CRM for marketing and investor outreach and sent multiple newsletters.

My role: I selected Zoho CRM, imported and checked more than 100 contacts, and set up ownership and follow-up tracking.

Work delivered

I tested the reporting workflow with an incoming email and confirmed delivery of a one-off PDF. The digest now runs weekly.

Explore the CRM import and reporting checks

Before the reporting workflow

From separate databases to one CRM.

I mapped fields from separate databases into a common Zoho CRM structure before importing the records.

Illustrative field mapping with fictional records

01 / Compare sources

Different labels, same meaning

Source A
Company: Cedar Example Co.
Contact Email: alex@example.com
Source B
Organization: Willow Sample Group
Work Email: sam@example.org

02 / Map fields

One record structure

Company or Organization
Maps to Organization
Contact Email or Work Email
Maps to Email

03 / Check the output

Make the record usable

Sample record
Cedar Example Co.
alex@example.com
What to verify
The email and organization match the source. If no owner is known, flag it for assignment rather than guess.

The existing walkthrough below picks up after import and follows activity from the contact record into the report.

Fictional import examples

Before the import: work through the exceptions.

Mapping the fields is only the start. Choose a record pair to see what needs a human decision before the CRM can support reliable follow-up.

Reconstruction of the documented test

Trace one activity through the system

Fictional contact and time.
Representative fields and report layout.

01 / Contact record

Start with a record built for follow-up.

Contact recordSample A
JM
Jordan Morgan

Example Ventures

Category
Investor contact
Owner
Relationship lead
Status
Follow-up needed
Next step
Review the latest activity and confirm the response.
Last activityTest activity not yet shown
Activity trail

Example activity A

Incoming email check

The test followed an incoming message through the existing contact record.

Report outputSample excerpt

Recent contact activity

Follow the activity to inspect its inclusion in the report.

Expected behavior

Documented observation

Validation and handoff

What was checked, delivered and configured

Incoming activityTimestamp update checked on the contact.Tested
Report inclusionThe test activity appeared in the report output.Tested
One-off PDF digestTest report delivery confirmed.Delivered
Weekly reportingThe PDF digest runs weekly.Recurring
Back to cases

04 / Executive materials & editorial QA

Make the claim precise.
Keep the versions aligned.

Investor materials needed to distinguish what the team had completed from what it was still planning.

My role: I produced and published the final versions, and handled the final English edit for materials going to investors and partners, including investor emails. I made translations read naturally without changing the underlying claims and kept the editable, HTML and PDF versions consistent.

Work delivered

Investors and partners received the English materials I finalized.

Explore the materials review

The final English edit

One milestone was complete. The next was still a plan.

Illustrative translation, not original company copy.

01 / Spanish source

Original meaning

“Ya terminamos la migración. La ampliación del acceso a más autores sigue prevista.”

02 / Literal English

Word for word

“We already finished the migration. The expansion of access to more authors is still planned.”

03 / Edited English

For the investor

“We’ve completed the migration. We still plan to give more authors access.”

Why this edit: “We still plan to” tells readers what the team intends without suggesting that more authors already have access.

Illustrative editorial examples based on documented review patterns. Not verbatim company copy.

Behind the work

Editorial judgment is part of quality control.

The challenge

A business presentation must serve an audience without getting ahead of the evidence. Stakeholder feedback can concern the substance of a claim, the meaning of a financial label or the visual hierarchy. Those are different problems and need different fixes.

My contribution

I worked through revisions at the page and phrase level, asked where changes had been made and checked how the result read. I challenged a completed technical milestone placed under a planned-version heading, requested exact change locations before publication and flagged a redundant label that disrupted the next item’s hierarchy. I directed and reviewed these changes; I did not perform the underlying technical migration.

The reasoning

A stronger sentence is not necessarily a bigger claim. The useful revision makes the actual status and intended meaning easier to understand. A layout correction is also substantive when a reader could otherwise connect a label to the wrong point.

What went out

I carried the materials through final editing and publication. The technical and financial owners remained responsible for approving the underlying facts.

Open a representative release checklist
  1. Confirm the underlying evidence and current status of each material claim.
  2. Resolve contradictory labels and assumptions across sections.
  3. Check editable, browser and PDF versions for consistency.
  4. Inspect small-screen reading, hierarchy and clipping.
  5. Record what changed and what still needs an owner’s decision.

Reconstructed checklist based on the review work.

From a technical discussion to a communication brief

Clarify the audience first

In a technical partnership discussion, I asked whether the deliverable was an internal briefing or an external proposal. That distinction changes the context, claims and decisions the document needs to contain.

Question premature commitments

I challenged language presenting a provider as selected before an agreement was settled, requested technical-owner input on outdated data-room information, and surfaced the trust and adoption concerns of nontechnical users.

Give the document a job

I helped define the brief around who the company is, why the technology matters and what kind of partner is sought, while reducing redundant sections. I was assigned to prepare the document.

Back to cases

05 / Institutional portal prototype

Turn an abstract request
into something reviewable.

Institutional and writer-contest workflows needed different content but a clear next step for each audience.

My role: I used stakeholder feedback to organize the content and navigation in English and Spanish.

Work delivered

A visual prototype for stakeholder review, translating requirements into an organized bilingual experience.

Explore the portal prototype

How I built it

Design the navigation around what a visitor needs to do.

I organized the English and Spanish prototype around the same sequence: understand the purpose, review the material and identify the next step. Keeping the same structure in both languages made the flow easier to compare in review. I checked the prototype on desktop and mobile.

Institutional workspace

Behind the work

A prototype makes the questions visible.

The challenge

Institutional and writer-contest workflows involve different audiences and types of information. The prototype provides a concrete way to discuss what belongs where rather than relying only on an abstract description.

My contribution

I used the prototype to make the navigation and content structure concrete enough for stakeholder feedback.

How to read the sample

Reconstructed bilingual example showing audience context, organized material and a clear next action.

Boundary and next step

The next implementation step would define permissions, integrations and technical requirements with the responsible team.

What I would clarify before implementation
  • Who is the primary audience, and what must they accomplish?
  • Which information is public, restricted or awaiting review?
  • What input or decision is needed at each step?
  • What is a prototype assumption versus an agreed requirement?

Why show service status?

I proposed bringing the service components into one client portal. A shared workspace would make them easier to find, but listing them together could also make a planned service look operational. The status labels keep that distinction visible.

Back to cases

06 / Supporting work / M2M Capital

From spreadsheet entries
to presentation material.

As a Data and Marketing Intern, I worked in Excel and PowerPoint on a shadow portfolio.

My contribution: I entered, organized and standardized spreadsheet data supporting performance and risk analysis, and helped prepare marketing and investor presentations.

Explore the spreadsheet and presentation work
01 / Organize

Make the source usable

Collect entries in a consistent spreadsheet structure. The documented work includes data entry and organization.

02 / Check

Make comparisons legible

A sample review might ask whether labels, dates and units are consistent before building a comparison view.

03 / Present

Explain, do not overstate

Turn selected spreadsheet information into clear marketing and investor-presentation material.

Illustrative workflow; original holdings, values and investor identities are omitted.

Scope

My scope was data preparation and presentation support.

Back to cases

The person behind the work

Curiosity, structure
and follow-through.

I’m Nico. I studied International Affairs at CU Boulder, with a focus on Latin America. My research there focused on China’s economic and diplomatic influence in the region and how the U.S. responded.

I bring those habits to business operations: check the source, make decisions traceable, and leave the next person a useful handoff.

I studied abroad in Seville, where I experienced firsthand what it takes to find your way through a new academic system.

Experience & resume

The broader background.

Download résumé ↓

PDF summary of experience, education and tools.

Mar 2026 – Present

Operations and Strategy Manager

Qantica

Built and managed the bilingual data room, from page layouts and revisions to publishing the approved figures.

Implemented Zoho CRM for 100+ investor contacts. The team uses it for outreach and newsletters, and the weekly digest summarizes CRM activity.

Wrote the implementation brief the team used to build the multimedia Showcase and refine it through later iterations.

Traced discrepancies in a 48-month financial model, corrected issues directly in Excel, and coordinated other fixes for review.

Produced final investor and public-facing materials and owned the final English edit, including investor emails. Made translations read naturally without changing the claims.

Created an English-Spanish portal prototype for institutional and writer-contest workflows and checked it on desktop and mobile.

Aug 2025 – Oct 2025

Business Planning Intern

Qantica

Supported business-plan development, scenario analysis, market research and presentation preparation for prospective investors.

Aug 2024 – May 2025

International Policy Research Assistant

University of Colorado Boulder

Researched China’s economic and diplomatic influence in Latin America and U.S. policy responses; synthesized primary and secondary sources into analytical briefs and presentations.

Dec 2020 – Aug 2021

Data and Marketing Intern

M2M Capital

Cleaned and standardized databases for performance and risk analysis; prepared marketing and investor presentation materials.

Education

University of Colorado Boulder
BA in International Affairs · August 2025

Languages

Native English and Spanish.

Tools

Zoho CRM, Excel, Word, Outlook, PowerPoint and Google Workspace. Excel work includes everyday formulas, sorting and filtering.

Working with assisted tools

ChatGPT, Claude and Manus support analysis, prototyping and output checks.

Contact

Start a conversation.

I’m interested in coordination, operations, and research roles that support international business, trade, or policy. If that sounds like your team, I’d like to hear from you.

Connect on LinkedIn

About these samples

Real work, with responsible boundaries.

The case studies describe my work. Interactive records, figures, and interfaces are illustrative. Confidential company data and third-party identities are omitted.