Contributed by Kia Fathi & Drew Moxon (Fifty Years)
At Fifty Years, we’re a small team of Happy Warriors that aim to have an outsized impact on the world. We have a lean and scrappy Product/Engineering team that is always focused on the highest value work: improving the lives of our founders and elevating our operational excellence. We run a program to help great scientists become great founders called 5050. Sorting through the tens of thousands of PhDs and postdocs to find good fits is a huge challenge. As a small team, automating workflows with high quality is critical.
We evaluated Lutra, Windmill, Retool, Gumloop, Browserbase, Zapier, Autotab, Intuned, and rolling our own platform when considering automation solutions.
We chose Lutra for the following reasons:
We evaluated the projected costs of our common workflows on Lutra and identified that we could save our team 71 working days of time per year with just our initial sets of automations.
For 5050, Lutra has become an integral part of our workflow. We utilize its powerful automation capabilities to manage and scale our talent identification initiatives. With Lutra, we can process large datasets, scrape thousands of websites for talented individuals, and enrich them with relevant information (LinkedIns, Career History, Contact Info), and classify and sort them.
We’ve been able to 2x our top of the funnel in just a few weeks of automating.
Airtable is one of our go-to tools for organizing and managing data. When combined with Lutra, it becomes even more powerful.
Lutra can read and update Airtable records, so it is great for enriching tables with data from the Internet or other sources Lutra can access.
As an example, suppose we have a table of company websites and we need to add company names and descriptions.
First, add new columns for “Company Name” and “Company Description”.
Next, start a new Lutra workflow and choose the “Summarize Company Websites” template.
Then, add the Airtable Data Connection.
Finally, run the workflow.
For more complicated enrichment, split the process into multiple Lutra workflows. This allows you to examine and fine-tune each step individually.
For example, suppose we want to find the latest news about each company from our previous example.
Add “Latest News Article URL” and “Latest News Article Headline” columns.
Create a new Lutra workflow, add the table as a Data Connection, and then give Lutra instructions on how to fill the new columns.
Find the latest news article about each company, and populate the Latest News columns.
Use AI to generate a few news search queries based on the Company Name and Company Description, to find news articles about the actual company instead of articles that just happen to have the company name as a word. For each article you find, check if it is actually about the company. Use the first article that you find that is actually about the company.
Finally, run the workflow.
If we wanted to further process the news results, we could make another workflow.
If the table is large or you need to add records and continuously enrich them, use Airtable filtered view to focus on precise subsets of data that need processing.
For example, in the workflow that populates “Company Name” and “Company Description” columns, use an Airtable filtered view of records with missing “Company Names" or “Company Descriptions".
Filtered views update dynamically as you add records to the table and as Lutra processes them, so you can simply run the workflow at any time, and Lutra will automatically pick up the records that need processing.
For complex data processing flows, it is useful to clearly delineate input and output in separate Airtable tables. This allows you to easily observe progress of records through our data pipelines in Lutra.
For records in Input Tables:
Processed
column to record which inputs have been processed.Error
column to indicate any issues with progressing them to the corresponding Output Table.For records in Output Tables:
Talent Website
in the example below)RECORD_ID()
in airtable to create unique ids for input records to reference like “foreign keys” in output records.Table 1: Talent Sources (Input Table)
Table 2: Talent (Output Table)
This structure lets us easily observe how records are progressing through our workflows and what sort of inputs are causing errors.
In summary, Lutra has proven to be an invaluable tool for our team at Fifty Years, helping us identify entrepreneurship-curious scientists in an extremely automated way. We’re excited to continue using it to streamline our talent identification pipeline and look forward to using its full potential in our other core workflows!
If you’re considering using a similar platform and have further questions, reach out: to kia@50y.com.
If you want to work with the next generation of great founders, we’re hiring at Fifty Years.