The author says that Hy4 Flash, GLM-5.3-Flash, and DeepSeek-V4.1-Flash each correctly calculated the totals and metrics for the same three sets of fictional ad data in WorkBuddy. Hy4 Flash's listed API input and output prices were lower than those of the two comparison models, but the post does not report token usage or measured costs for this session, so the listed prices cannot show how much this run actually saved.
Suitable for assessing: The CPC, conversion rate (CVR), and cost per lead (CPL) calculations for the three sets of fictional ad data in the post, as well as the response times reported by the author.
Not suitable for extrapolating to: General math ability, accuracy, quality, or speed rankings on other ad datasets or WorkBuddy tasks. API list prices also cannot stand in for the cost of an individual task.
Model versions covered: Hy4 Flash, GLM-5.3-Flash, and DeepSeek-V4.1-Flash-1017 (the name shown in the pricing section).
Test environment or client: WorkBuddy; the client version, tool settings, and model interfaces are not specified.
Reasoning level and parameters: Not specified.
The author says they gave the same three fictional ad campaigns to all three models and asked them to calculate CPC, CVR, and CPL; one campaign had no leads. The post does not provide each campaign's spend, clicks, or leads, nor the prompt, model parameters, run order, or number of repetitions. The author reports that all three produced correct arithmetic and lists the totals and aggregate metrics.
The author reports total spend of USD 1,350, 650 clicks, and 27 leads.
Aggregate CPC = 1,350 / 650 = USD 2.0769, or about USD 2.08; aggregate CVR = 27 / 650 = 4.1538%, or about 4.15%. GLM reported 4.2%, which the author considers acceptable at either level of precision.
Aggregate CPL = 1,350 / 27 = USD 50. The campaign with zero leads should not have a CPL of 0: spend / 0 is undefined, so it should be marked as undefined or as having no cost per acquired lead available.
The author says all three models handled the zero-lead case correctly; the calculations for individual campaigns are not shown.
The author reports that DeepSeek took 7 seconds, while Hy4 Flash and GLM each took 19 seconds. These are self-reported timings from a single run; the post does not specify the start and end points or whether tool wait time was included.
The post lists uncached API prices per million tokens (RMB input / output): Hy4 Flash ¥0.5 / ¥2; GLM-5.3-Flash ¥0.8 / ¥2.8; and DeepSeek-V4.1-Flash-1017 ¥1 / ¥4 off-peak and ¥2 / ¥8 at peak. At those listed prices, Hy4 Flash's input price is 37.5% lower and its output price about 28.6% lower than GLM's. Compared with DeepSeek's off-peak prices, both input and output prices are 50% lower.
| Item | Value reported in the post |
|---|---|
| Total spend | USD 1,350 |
| Total clicks | 650 |
| Total leads | 27 |
| Aggregate CPC | USD 2.08 |
| Aggregate CVR | 4.15% (GLM reported 4.2%) |
| Aggregate CPL | USD 50 |
| DeepSeek / Hy4 Flash / GLM response time | 7 sec / 19 sec / 19 sec |
The API prices are unit prices listed in the post, not measurements of the cost for this WorkBuddy run. The author did not disclose token counts, cache hits, reasoning tokens, number of calls, or billing, so the actual cost of this run is unreported. The price comparison uses only the time periods and uncached input and output prices listed in the post.
This is a personal report from a Reddit user. It provides a same-task comparison across three models, aggregate data, response times, and a pricing basis, but no per-campaign inputs, raw model outputs, or run logs, so its accuracy and timing cannot be independently verified.
The totals can be used to recalculate the reported aggregate CPC, CVR, and CPL; that does not make it possible to recalculate each campaign's answer. The post does not provide enough raw data to check each result.
CPL for a campaign with no leads is undefined, not zero. The author says no model returned zero for it, but does not show the relevant responses; this is based on the author's account.
The author does not disclose any relationship with the model providers, WorkBuddy, or API providers, or say whether the post was sponsored or promotional. No sponsorship disclosure is visible in the post body. Any potential conflict of interest cannot be confirmed from this information.
DeepSeek was faster in this single task, and all three models were reported to get the calculations right. The sample size, task difficulty, and timing method do not support broader conclusions about speed or accuracy.
API list prices are not measured costs for this task. Input and output length, caching, reasoning tokens, and retries could all change the actual cost.
Reproducing the results for each ad campaign would require the three sets of raw spend, click, and lead counts, along with the original prompt, WorkBuddy version, exact model snapshots, and run configuration, none of which the author provided. Verifying response times and actual costs would also require timestamped run logs and the input, output, reasoning-token, and cache usage for every call. The available information supports only recalculating the reported aggregate metrics and doing the arithmetic comparison of the API prices listed in the post.
Hy4 Flash