5 weeks to deliver two sites after the previous developer left | 65 hours under the agreed hour cap | 24+ months of maintenance signed by the end client after launch
\n\n
A small marketing agency from Chicago lost its freelance developer two weeks before the deadline for two websites for a financial services client. The client hadn’t seen a single preview. We agreed a realistic deadline with the agency, prepared arguments for the conversation with the client, and delivered both sites in five weeks with two developers and a project manager. The project used 365 of the 430 hours budgeted, and the client signed a maintenance package for at least 24 months.
\n","csExecutorsTitle":null,"csExecutorsExists":null,"csExecutors":null,"csEffectsTitle":"The situation","csEffectsMockup":{"altText":"Weekly white label report: 365 of 430 capped hours used, weekly reports and calls over 5 weeks, 2 developers and a project manager","atttachement_pl":{"altTextPl":null},"srcSet":"https://super-tajny-headless-cms.bravenew.agency/app/uploads/2022/10/white-label-wordpress-project-takeover-status-before-519x768.png 519w, https://super-tajny-headless-cms.bravenew.agency/app/uploads/2022/10/white-label-wordpress-project-takeover-status-before-865x1280.png 865w, https://super-tajny-headless-cms.bravenew.agency/app/uploads/2022/10/white-label-wordpress-project-takeover-status-before-768x1137.png 768w, https://super-tajny-headless-cms.bravenew.agency/app/uploads/2022/10/white-label-wordpress-project-takeover-status-before.png 989w","sourceUrl":"https://super-tajny-headless-cms.bravenew.agency/app/uploads/2022/10/white-label-wordpress-project-takeover-status-before.png"},"csEffectsList":"The agency had hired a freelancer to build two websites for a financial sector client. The sites were similar and built from repeating components. Communication with the freelancer was poor from early on: updates came late and the agency rarely got any feedback. Two weeks before the deadline, the freelancer told the agency they wouldn’t finish the project for personal reasons.
\nAt that point the client hadn’t seen any previews. The project had looked fine at the start, so the sudden lack of progress made the client impatient. The agency was at risk of losing the client, along with future income from maintaining and developing the sites. Financial sector clients expect work based on facts and fixed dates, which made the delay even harder to explain.
\n","csEffectsExists":true,"csEffects":null,"csBeforeAfterTitle":null,"csBeforeAfterExists":null,"csBefore":null,"csAfter":null,"csAboutTitle":"Agreeing on a deadline we could meet","indentedSectionTitle":"What we built?","indentedSectionSubTitle":null,"indentedSectionImage":{"altText":"Wordpress development - working on website","atttachement_pl":{"altTextPl":"Wordpress development - praca nad stroną internetową"},"srcSet":"https://super-tajny-headless-cms.bravenew.agency/app/uploads/2025/04/DSC09637-Poprawione-Szum-512x768.jpg 512w, https://super-tajny-headless-cms.bravenew.agency/app/uploads/2025/04/DSC09637-Poprawione-Szum-854x1280.jpg 854w, https://super-tajny-headless-cms.bravenew.agency/app/uploads/2025/04/DSC09637-Poprawione-Szum-768x1152.jpg 768w, https://super-tajny-headless-cms.bravenew.agency/app/uploads/2025/04/DSC09637-Poprawione-Szum-1024x1536.jpg 1024w, https://super-tajny-headless-cms.bravenew.agency/app/uploads/2025/04/DSC09637-Poprawione-Szum.jpg 1067w","sourceUrl":"https://super-tajny-headless-cms.bravenew.agency/app/uploads/2025/04/DSC09637-Poprawione-Szum.jpg"},"indentedSectionExists":true,"indentedSectionDescription":"Both sites were built in Elementor and ACF Pro, based on the agency’s design.
\nThe most demanding part was the fund data. The sites show daily prices, monthly, quarterly and yearly performance, holdings, cash positions and a growth of $10,000 chart, broken down by fund and share class. All of it updates without anyone at the agency or the client touching the site.
\nWe wrote the data processing from scratch. The data provider delivers CSV files straight to the server, and two PHP scripts run on a schedule (cron) to process them. The main parser reads each file, adds the data the source files don’t include with the help of a second script, builds a file in the structure the site expects and replaces the previous version. Charts and tables on the site then show the new figures. Each data type has its own run, so daily prices, holdings or quarterly performance can be processed or rerun separately.
\nIf a delivery comes in without new data, the parser stops, the current figures stay on the site, and we get an email notification. Neither the agency nor the client has to check whether the data came through.
\n\n
5 weeks
\nBoth sites were delivered within the new deadline agreed with the agency and its client.
365 of 430 hours
\nThe project closed 65 hours under the agreed cap, and the agency paid only for the hours worked.
24+ months
\nAfter launch, the end client moved to continuous support of 10–20 hours a month, which has now lasted more than 24 months.
What happend next?
\nThe agency still works with us.
\n
After reviewing the scope, we told the agency right away that two weeks wasn’t enough. Besides the sites themselves, the project included charts presenting the company’s financial data and daily automatic data updates, based on files uploaded to the server.
\nWe agreed a new deadline with the agency and prepared a line of argument they could use with their client: what the scope actually includes, why it needs more time, and what the client would receive and when. Once the client accepted the new date, we started work.
\n","csStructuredData":null}}},"pageContext":{"id":"cG9zdDoxMjA0Nw==","language":"en","contentType":"case-study","translations":[]}}, "staticQueryHashes": ["2032659661","2211443699","2356763386","2521492788","2633806262","2697845365","3343017907","3379812759","3806438429","3851734465","3985950302","3991507469"]}