Meet the Team

Tanya is Orchid's driving force. For over three decades, she has accomplished an extraordinary career defined by her ability to consistently guide client teams through their most challenging implementations. Tanya's expertise as a solution architect and strategist is unmatched. She is renowned for her grasp of intricate details and remarkable ability to distill complex ideas through vivid metaphors. Beyond her business prowess, she is a passionate potter and a culinary enthusiast, indulging in the occasional extravagant meal.

Amilcar leads multi-year Salesforce implementations and data migrations, specializing in organizations that are already tired. He bakesthe same shortbread recipe weekly, studies oralhistory as a method of damage control, and lives with a partner who refuses to use the CRM.Amilcar volunteers recording communityinter views and never edits out long pauses.

Gabriel builds and maintains Salesforce integrations that move data quietly and correctly. Hepresses flowers in finished books, studies memory formation, and keeps both beside old interface diagrams. Gabriel volunteers at a senior center and listens without correcting timelines.

Svet maintains servers with quiet vigilance and assumes that anything working isalready in danger. He documents fixes no one will read, names machines after weather events, and monitors logs the way others watch crime dramas. Svet restores outdated laptops, studies redundancy for comfort, and volunteers to reboot community center computers before anyone asks.

Nolan translates undocumented business habits into Salesforce workflows that users recognize but cannot quite explain. She enjoys feeding birds that may be imaginary, studies anthropology focused on unspoken rules, and walks a dog that stops at the same places every night. Nolan helps organize neighborhood events and quietly moves loud activities farther away.

Paul designs Salesforce data models intended to survive staff turnover and memory loss –doesn’t account for his own short term memory issues. He collects smooth stones, studies obsolete maps, and consults a specific river rock before approving custom objects. Paul volunteers teaching geography and reminds people that systems outlast intentions.

Matheus manages Salesforce project logistics, documentation, and task sequences that neverfully resolve. He maintains unfinished lists, studies domestic history, and texts them to a friendfor reassurance. Matheus volunteers helping neighbors move and labels boxes beyond necessity.

Rodolfo writes Apex with cautious precision and assumes every edge case ispersonal. He refactors legacy code like an archaeologist with a deadline, studies data models the way others study maps, and keeps a sandbox that exists purely to feel safe. Rodolfo restores broken automations, names variables after emotions,and volunteers to debug problems that begin with “this should be simple.”

Atoni tests Salesforce configurations for subtle failures and improbable outcomes. She proofreads menus, studies semiotics, and exchanges annotated photos with her mother. Atoni volunteers reviewing resumes and erases comments before returning them.

Sonia implements Salesforce solutions with a focus on permissions, reporting, and explaining to executives why something cannot be “just one checkbox.” She enjoys collecting hotel stationery she has not paid for, studies threshold spaces in literature, and maintains a long-standing relationship with a ficus that reacts poorly to deployments. Sonia volunteers at a communitygarden, where she labels plots more thoroughly than required.