NFNicolas FerroSelected work

Nicolas Ferro / Selected work

Project coordination
and business operations.

At Qantica, I set up a bilingual data room, coordinated corrections to a 48-month financial model, and implemented a Zoho CRM workflow for more than 100 investor contacts.

Native English & Spanish · BA, International Affairs, CU Boulder

Professional portrait of Nicolas Ferro wearing a suit and tie against a neutral background
Nicolas Ferro

Seven case studies

Selected work.

Featured / Qantica data room

A bilingual data room
built to handle change.

Not every requested edit should become an immediate change. I structured the bilingual experience and directed updates around current sources, clear owners and deliberate approval points.

See the decisions, brief and handoff →

Revision triage / Composite reconstruction

01

Proceed now

Approved summary replacement
Matching translated text

02

Await approved source

Model-dependent cards
Charts and tooltips

03

Owner decision

Technical-plan changes
Unresolved dependencies

Open any case to see the decisions, checks, and work behind the result.

A focused pathwayInternational perspective. Clear coordination.Explore selected work for international programs & program support ↓

I bring an International Affairs background, native English and Spanish, and practical experience turning complex business material into organized briefs, workflows and stakeholder handoffs.

  1. 01 / Planning & stakeholder handoffs

    From a broad request to a reviewable plan.

    A seven-part planning matrix connected requirements, inputs, owners and open decisions before technical implementation.

    Explore project coordination →
  2. 02 / Bilingual information design

    Make information useful across audiences.

    An English-Spanish institutional portal prototype translated stakeholder requirements into clear content, service stages and next steps.

    Explore the bilingual prototype →
  3. 03 / Briefing & editorial review

    Keep the message aligned with the evidence.

    Business-material revisions clarify claims, preserve consistency across versions and turn stakeholder feedback into specific changes.

    Explore communication & review →

Further example: data-room structure & change control →

Background and perspective

BA in International Affairs, University of Colorado Boulder. Native English and Spanish. Personal study-abroad experience in Seville adds a firsthand perspective on studying in another country.

Résumé & experience → Contact →

Featured case / Data-room setup & change governance

A decision resource,
not just a document store.

A bilingual data room has to remain coherent while the business model, financial assumptions and stakeholder feedback change. A revision that looks reasonable on one page can create contradictions elsewhere.

My contribution: I set up the data-room experience and directed its content structure and revision process. I translated feedback into scoped implementation instructions, checked the relationship between source material and site content, and separated approved changes from unresolved decisions.

Work produced

A data-room asset and controlled update specifications: page scope, bilingual requirements, source checks and review gates.

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.

Verify a defect before rebuilding

A reviewer reported a broken workbook preview. I identified that the limitation was in the review tool’s access, not the working preview. The appropriate action was verification, not an unnecessary rebuild.

Match detail to the change

I asked for a simple executive-summary replacement where that was enough, and detailed instructions for the page actually being rebuilt. 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. Verify a reported defect before treating it as a rebuild request.

Handoff

Pass the implementation tool only the approved, page-specific changes and translations. Keep unresolved decisions with their owners rather than burying them in a broad prompt.

Review

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

Illustrative reconstruction

Follow a change before approving it

Reconstructed example of the review approach; labels are generalized.

Source of truth→Affected content→Owner & approval→Bilingual review

Interactive reconstruction

Which changes are safe to release?

I split a 41-page revision packet into changes that could proceed and changes that needed a fresh source or a check in both languages. Move the same change set through those gates.

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 provided the structure, requirements, corrections and approval. Drafting and implementation tools supported execution, with technical decisions assigned to their owners.

↑ Return to selected work

Organized project requirements
into a technical brief.

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 consolidated a seven-part planning matrix, organized input requests and decision owners, and prepared a mobile-first brief for technical review.

Work delivered

A seven-tab planning matrix and mobile-first implementation brief, with first-release scope, input needs, decision owners and technical questions.

Explore the planning brief

Anonymized reconstruction of actual planning work

Follow the interactive teaser from request to handoff

Original planning statuses retained.
Project and people generalized.

↑ Return to selected work

Coordinated corrections
across a 48-month model.

A 48-month forecast contained inconsistent periods, formula references and summary figures. Some discrepancies were spreadsheet repairs; others required a decision about the business assumption.

My role: I organized the review, requested cell-level explanations, coordinated corrections and prepared the changes and open questions for management.

Work delivered

Documented period and reference corrections across the model, with unresolved budget assumptions and metric definitions separated for management review.

Explore the forecast review

How the model works

Turn a runway estimate into something you can check.

In the forecast review, I asked for cell-level explanations and separated calculation corrections from changes that needed a business decision. This simplified example shows why that distinction matters: the same cost base supports different runway estimates depending on what you count as revenue.

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 review desk

Recalculate the number, or ask for a decision?

In the 48-month review, a formula repair and a scope decision could both look like a wrong total. Choose a finding and see what you can actually resolve.

Reconstructed cases / Illustrative figures

Inspect the issue, its dependencies and the handoff

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.
↑ Return to selected work

Implemented contact tracking
and tested the reporting flow.

The investor workflow needed structured records, clear follow-up and a practical way to surface activity for leadership.

My role: I selected and implemented the CRM, imported and checked more than 100 contact records, configured ownership and next-step tracking, and tested the activity-to-report path.

Work delivered

More than 100 checked contact records, ownership and follow-up fields, a delivered PDF test digest and a configured weekly reporting schedule.

Explore the CRM import and reporting checks

Before the reporting workflow

From separate databases to one CRM.

I consolidated contact information from separate databases for Zoho CRM, then imported and checked more than 100 contact records. The goal was not just a single list. Each record needed to support ownership, follow-up and reporting.

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 reportingNative recurring schedule verified.Configured
↑ Return to selected work

04 / Executive materials & editorial QA

Make the claim precise.
Keep the versions aligned.

Business presentations change as product plans, evidence and feedback develop. A polished slide is not enough if the wording promises more than the underlying work supports.

My role: I revised investor-facing materials, worked through stakeholder feedback and checked consistency across editable, HTML and PDF versions.

Work delivered

Revised materials and page-specific change explanations, including clearer status language, financial terminology and layout corrections.

Explore the materials review

How I reviewed it

Check the source, then follow the change.

I reviewed changes at the page and phrase level and asked for exact change locations so I could check the editable, HTML and PDF versions against each other. A useful review trail says what changed, what must match and what still needs approval.

Illustrative release check with fictional figures

01 / Source change

A model assumption changes

The approved forecast moves a planned cost from Month 11 to Month 12. The full-year cost is unchanged, but its monthly placement changes.

02 / Before and after

Update the figure and its meaning

Before
“Planned cost: Month 11.” The chart also shows it in Month 11.
After
“Planned cost: Month 12.” Move the chart entry and verify that the annual total still includes it.

03 / Release check

Catch the stale copy

Compare the slide, browser view and exported PDF to the approved source. If the Spanish caption still says Month 11, flag that version as not ready, even if its chart is correct.

Example handoff: Record the source version, affected page and language, and the remaining correction. Send that record with the revised materials for sign-off.

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.

The handoff

Revised material and a page-specific change record, ready for review before publication.

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.

↑ Return to selected work

05 / Institutional portal prototype

Turn an abstract request
into something reviewable.

A portal concept needs more than attractive screens. It needs an understandable structure for its audience, content and next steps.

My role: I developed a bilingual institutional portal prototype and used stakeholder communication to clarify what it should explain and support.

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.

New illustrative sample of the information structure. Generic content replaces proprietary material.
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 created an English-Spanish visual portal prototype and checked its content and layout on desktop and mobile. The prototype turned stakeholder requirements into a bilingual navigation and content structure the team could review.

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?

Beyond the screen: staged service requirements

Consolidate the workflow

I proposed bringing service components into a client portal, with an initial approval status, returned reports and a visible distinction between available and future components.

Make maturity visible

A prototype should not imply that every visible module is operational. The requirement is to distinguish available, awaiting approval and future functionality so stakeholders can assess scope accurately.

From prototype to implementation

The deliverable combines workflow requirements with a bilingual visual prototype for review.

↑ Return to selected work

06 / Supporting work / M2M Capital

From spreadsheet entries
to presentation material.

As a Data and Marketing Intern, I supported data preparation for a shadow portfolio and the materials used to explain it. The work involved Excel data management and PowerPoint marketing and investor presentations.

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

Spreadsheet preparation supporting performance and risk analysis, plus marketing and investor-presentation materials for a shadow portfolio.

↑ Return to selected work

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 work involved turning complex material into clear briefs and presentations.

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

I work in English and Spanish. I’m interested in junior opportunities where careful analysis, clear communication and coordination help a team move its work forward.

Make ambiguity actionable

Separate requirements, assumptions and open decisions before a handoff.

Check the underlying detail

Trace inconsistencies through source material, calculations and versions.

Connect information to people

Document owners, follow-up and the next action, not just a list of tasks.

Make work reviewable

Use briefs, prototypes and examples so stakeholders can respond to something concrete.

Experience & resume

The broader background.

Download résumé ↓

PDF summary of experience, education and tools.

Mar 2026 – Present

Operations and Strategy Manager

Qantica

Reviewed a 48-month financial model for inconsistencies in revenue scenarios, staffing and cash flow; coordinated corrections for management review.

Revised investor materials using stakeholder feedback and kept editable, HTML and PDF versions consistent.

Selected and implemented a CRM for 100+ investor contacts, with ownership and follow-up tracking; configured activity reporting.

Coordinated follow-up on website and cloud-migration plans, documenting requirements, task dependencies and unresolved decisions.

Created an English-Spanish visual portal prototype for institutional and writer-contest workflows; checked content and layout on desktop and mobile.

Communicated directly with authors, investors and production companies.

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. The case studies focus on the questions, decisions and checking work, not unsupported claims of independent software engineering.

Contact

Start a conversation.

I’m happy to talk about project coordination, operations, and international programs.

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.